All the Perl that's Practical to Extract and Report
use Perl Log In
dws (341)
A Sloooow Install
Installing and configuring Linux is something I do infrequently enough to forget a lot of little details, like "This is going to be a headless system. How do I not start X?" (Answer: Edit
Moving bits off to a backup server before repartitioning (to make a proper
Now I'm waiting while the CDs spin, after which I'll struggle through more small stuff I've forgotten, like how to set up MySQL and PostgreSql, and which settings in httpd.conf need tweaking. Then comes the fun part: Sorting out what's changed in mod_perl land between RH8 and FC3.
Part of me thinks I should do this more often.
Or is it a BUG?"
"Let's call it an accidental feature. :-)"
--Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
“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, som