Alan wrote:
Is there any place
that stores the output of this so that it can be looked at later?
Perhaps you'd like to give remote logging an opportunity?
HTH,
Norberto
--
Linux 2.6.2-rc2-mm2 Pentium III (Coppermine) GenuineIntel GNU/Linux
03:47:58 up 4:22, 1 user, load average: 0.23,
I have a server with the kernel append line having panic=30 which
reboots the box 30 seconds after a kernel panic. However, once it
reboots I have no way to see what the problem was. Is there any place
that stores the output of this so that it can be looked at later? I
know that the dmesg
On Tuesday 03 Feb 2004 01:12, Alan wrote:
I have a server with the kernel append line having panic=30 which
reboots the box 30 seconds after a kernel panic. However, once it
reboots I have no way to see what the problem was. Is there any
place that stores the output of this so that it can be
Add this to /etc/conf.d/local.start:
echo Saving dmesg output to /var/log/dmesg...
echo /var/log/dmesg
echo #
/var/log/dmesg
date /var/log/dmesg
dmesg /var/log/dmesg
Thanks peter, but this only deals with boot messages, I'm
On Tuesday 03 February 2004 08:14, Alan wrote:
Thanks peter, but this only deals with boot messages, I'm looking for
the kernel panics and whatnot that are thrown there by the kernel just
before the box crashes horribly :)
Try adding the same into /etc/conf.d/local.stop Provided that the box
On February 2, 2004 Alan[EMAIL PROTECTED] wrote:
Thanks peter, but this only deals with boot messages, I'm looking for
the kernel panics and whatnot that are thrown there by the kernel just
before the box crashes horribly :)
There are lots of kernel debugging howto pages out there, here's one:
