On 26/03/04 00:49 +0530, Jemshad O K wrote: > > On Wed, 24 Mar 2004 15:32:58 +0530, "Suresh Ramasubramanian" > <[EMAIL PROTECTED]> said: > > >>>>> "Jemshad" == Jemshad O K writes: > > > > Jemshad> tried disabling crond and atd ? > > > > Nice. Sounds a lot like "I can't find where you sprained your leg, so > > I'll just cut the leg off". > > It my way of doing. When I am in a trouble, the first thing I am going to > do is fix that first - not to go for the root cause of it. Once I fix Wrong attitude. You need to figure out the root cause of the problem, and then make sure it does not happen again.
> that, removing something that I suspected, then I can make sure that > those were the problem areas. > > And, what I posted is just my suggestion - its not necessary that you > must do that way. Its upto you to decide on whether or not to follow > that. > > I am a system administrator and we once had a server with a very similar > problem - it went for reboot every morning at 8.30 am IST ( the server's > time - 4:00 am ). It was very peculiar and after lot of research, we > found nothing and we started updating all packages and kernel and it was > somehow fixed. Sure sounds like a cron issue to me. Lets see, at 4 am, I have updatedb and the log analysers running. Either one of those could have been the cause of the reboot, or maybe just the two together overloaded the box, and had it get OOM. Or hit a bad segment of memory and caused an oops. But you have not found the problem at all :) Devdas Bhagat ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ linux-india-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/linux-india-help
