Date: Tue, 16 Sep 1997 08:37:38 +1000 (EST) From: "Daniel O'Callaghan" <danny@panda.hilink.com.au> To: Robert Eckardt <roberte@MEP.Ruhr-Uni-Bochum.de> Cc: hackers@FreeBSD.ORG Subject: Re: A crash that isn't Message-ID: <Pine.BSF.3.91.970916083647.818C-100000@panda.hilink.com.au> In-Reply-To: <199709152129.XAA04723@ghost.mep.ruhr-uni-bochum.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 15 Sep 1997, Robert Eckardt wrote: > Hi, > > looking at lastlog today I was a bit surprised to find a machine have > "crashed". > [...] > roberte ttyp0 134.147.6.3 Mon Sep 15 13:02 - 13:16 (00:13) > reboot ~ Mon Sep 15 12:47 > roberte ttyp0 134.147.6.3 Mon Sep 15 12:47 - crash (00:00) > shutdown ~ Mon Sep 15 12:40 > roberte ttyp1 134.147.6.3 Mon Sep 15 12:22 - shutdown (00:18) > [...] > > In fact, the machine (running 2.2.2) was halted at 12:40. > After reboot at 12:46:20 I logged in as soon as the tty became available > (at 12:47) and obviously before the reboot was logged. > > (It would be a new record to boot the machine in less than 1 min > w/o additional entries in the logs -- esp. as it waits 30s for the > tape to become ready. :-) > > Can the late logging of reboot be responsible for this strange crash entry ? Looks like it to me. Question is, how come you managed to log in before the ~reboot entry was added. /* Daniel O'Callaghan */ /* HiLink Internet <http://www.hilink.com.au/>; danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.970916083647.818C-100000>