On Mon, 14 Feb 2000, chris smith wrote: > so you just learned something very valuable, that Linux needs to be > rebooted too to clead up after it's self. despite what you may hear it > needs it more often than you think, especaily if it is doig something > other than just sitting there. Not particularly. After you have worked as a professional sysadmin for awhile, you will learn that the number one priority is to reduce downtime. If a reboot will solve your problem quicker then figuring out what process has gone off the trolley and wedged itself, then by golly, you reboot. (This assumes, of course, you do not have anything running on the machine that will not recover from a reboot.) In my experience, Linux can clean up after itself quite well. However, there are times where you have to know what usermode utilities to run to clear up usermode problems (e.g., a wedged NFS daemon). In such cases, rebooting (or transitioning to single-user mode and back again) often fixes the problem by brute force. Whatever works. Compare this to Windows NT, which needs to be rebooted to: - Install new software - Remove old software - Change the network configuration - Add or remove a modem - Change the video driver Then there are all of the *forced* reboots you have to endure when it bluescreens on you. There really isn't any comparison. -- Ben Scott [EMAIL PROTECTED] ********************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the following text in the *body* (*not* the subject line) of the letter: unsubscribe gnhlug **********************************************************
