NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
:-)
--Larry Wall in <1991May31.181659.28817@jpl-devvax.jpl.nasa.gov>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
“What are those processes?” (Score:1)
Here's a nice tip for Linux:
An easy to remember combination of switches that means “list listen sockets”, “print the name and PID of the corresponding process”, and “TCP sockets only”, respectively. The
-pfor showing the process names is the trick here of course. Then you just go grepping init scripts.Re:“What are those processes?” (Score:2)
That beats netstat -a | less by a bit. The problem for me, though, is sorting through all of those processes (and FC3 seems to have added some new ones), deciding which are really important. Why do I have an nfslock process without nfs? Do I really need rpc stuff? (Probably No.) Etc.
That's the problem with picking this stuff up every few years rather than weekly or monthly. (Other than periodically installing updates, which I do, having learning the hard way that even if I ignore an openssh exploit, some teenager in elsewhere won't.)
Reply to This
Parent