On Mon, Mar 10, 2003 at 10:01:00AM +0100, Jan Johansson wrote: > Is there someway to find out what caused a system reboot? I have the > following in my "last" > > argus:~# last -20 > root pts/0 192.168.221.207 Mon Mar 10 08:11 still logged > in > reboot system boot 2.4.18-bf2.4 Sun Mar 9 17:49 (16:06) > > root pts/0 192.168.221.207 Fri Mar 7 16:31 - crash > (2+01:18) > > But i cant find anything in the logs which shows why the system was > rebooted. What worries me more is that I should be the only one with > root access to this system, which Is a minimalistic Debian/Testing doing > not much else then running shorewall.
Two things: 1) You might try building or installing a new kernel for that thing; you're still running the installer kernel which is certainly not optimal for your specific hardware. 2) I wouldn't worry so much about it crashing unless it happens again. If it does crap out again, apt-get install either memtest or memtest86, depending upon whether you can live without this machine being used for an evening. Bad RAM or a bad power source is most often the source of instability, in my experience. -troy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
