Actually, on a prodction server (or some embedded systems even) what you really want to do in case of a kernel panic is not to reboot , but rather to log the panic and THEN reboot so that you can have a good idea on what caused the problem without booting again and loosing the all important 5 nines uptime.
That's what the Linux Kernel Crash Dump patch and tool does. You can find it here: http://lkcd.sourceforge.net/ Indeed, one of my main gripes with the so called Enterprise version of Redhat (and others? I don't know) is that they don't include this. Which means that if a client has a crash the only way to know what happened is to re-create the crash. A really bad idea IMHO in a prodcution environment. Cheers, Gilad -- Gilad Ben-Yossef <[EMAIL PROTECTED]> Codefidence. A name you can trust (tm) http://www.codefidence.com "I am Jack's Overwritten Stack Pointer" -- Hackers Club, the movie ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
