Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #67191
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Newsgroups | comp.os.linux.misc |
| Subject | “My 5 Go-To Linux Commands For Troubleshooting” |
| Date | 2025-04-22 23:23 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <vu98df$1kqer$1@dont-email.me> (permalink) |
Jack Wallen is at it again, with another article introducing some commands useful for diagnostic purposes <https://www.zdnet.com/article/my-5-go-to-linux-commands-for-troubleshooting-and-how-i-use-them/>. One thing I recently discovered is dmesg has the “-T” option. This shows the message times as regular date/time stamps, instead of seconds after boot (but note the limitations documented in the man page). As for his use of the “ps” command, I would say, ignore the obsolete BSD-style options with no hyphens. Use more modern forms like “ps -ef” instead. Also, if you want more accurate displays of process start time and elapsed times, you can specify custom output options, like “-o user,pid,ppid,lstart,etime,cmd”.
Back to comp.os.linux.misc | Previous | Next — Next in thread | Find similar
“My 5 Go-To Linux Commands For Troubleshooting” Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-04-22 23:23 +0000
Re: “My 5 Go-To Linux Commands For Troubleshooting” rbowman <bowman@montana.com> - 2025-04-23 03:00 +0000
Re: “My 5 Go-To Linux Commands For Troubleshooting” Allodoxaphobia <trepidation@example.net> - 2025-04-24 13:36 +0000
csiph-web