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 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. So what I meant here was, if it is not something that went through atd or cron, the machine does have some serious problem. Hope this is clear !. -- Jemshad O K http://jemshad.com System Administrator Deru Communications http//deru.net @(-_-)@ "I know Karate, Kung Fu, and 47 other dangerous words" -- http://www.fastmail.fm - Sent 0.000002 seconds ago ------------------------------------------------------- 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
