On Sun, Nov 04, 2001 at 05:07:33AM -0500, Branden Robinson wrote: > > simplest way to deal with it is run lsof +L1 after an upgrade and > > kill/restart all offending processes. > > Like your X server? :) yup, i always restart X immediatly after its upgraded, if the upgrade broke it i want to know about it right away, not days or weeks later when it gets restarted for some other reason. besides that and security updates in X won't take affect until the old one is killed. > > in which case you will have an increasing supply of cruft as time goes > > on? especially if reboots happen less then every 8 monthes. > > Or you can periodically take the box down to runlevel 1 and take care of > it. Besides which, gaping security holes are found in the kernel with a going to runlevel 1 is rarly needed. usually its only one or two processes, no big deal. > greater frequency than once every 8 months, so you'll be rebooting > to upgrade it anyway. thats a bit cynical. i run 2.2 anyway, it just got its first security update in 8 monthes. -- Ethan Benson http://www.alaska.net/~erbenson/
Attachment:
pgpEkZ7QN_0Hb.pgp
Description: PGP signature