This is killing me. I come from the windows world where we deal with bugs almost daily. The rule seems to be to patch the bug, then patch the patch to fix the bug, then patch the patch to fix the patch to fix the bug and finally install the patch to fix the original problem since it was re-introduced in the series of patches to fix the patches. I am so disgusted with having to constantly keep on top of the patches, especially the ones that require the server to be rebooted. And your solution to Red Hat is to find the problem and fix it once and for all! It is almost sickening to hear that there is actually a solution. Well, may my install of Linux do as well. Thanks for the confidence folks. Buck > -----Original Message----- > From: shrike-list-admin@xxxxxxxxxx > [mailto:shrike-list-admin@xxxxxxxxxx] On Behalf Of Scot L. Harris > Sent: Wednesday, October 08, 2003 12:07 AM > To: shrike-list@xxxxxxxxxx > Subject: Re: How to know when to reboot the server > > > > On Tue, 2003-10-07 at 22:06, Ow Mun Heng wrote: > > Hey all, > > > > Lame o question. Server's running RH8 for 49 days > already. I'm not > > sure when I need to re-boot the machine. Anyone has any > > rule-of-thumb?? > > IMHO a properly configured system should not need to be > rebooted. When you have to upgrade the kernel should be > often enough. If you find that you do have to reboot the > system on a regular basis to "fix" something then you need to > dig into that problem and fix it for real. > > > -- > Shrike-list mailing list > Shrike-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/shrike> -list > > > -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
