Date: Sat, 14 Feb 2004 17:10:54 +0300 From: Sergey 'DoubleF' Zaharchenko <doublef@tele-kom.ru> To: Barbish3@adelphia.net Cc: John DeStefano <deesto@yahoo.com> Subject: Re: reboot record information Message-ID: <20040214171054.10e8f6ba@Hal.localdomain> In-Reply-To: <MIEPLLIBMLEEABPDBIEGEEPIFKAA.Barbish3@adelphia.net> References: <20040213155654.64692.qmail@web40606.mail.yahoo.com> <MIEPLLIBMLEEABPDBIEGEEPIFKAA.Barbish3@adelphia.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Signature=_Sat__14_Feb_2004_17_10_54_+0300_SlvrNU.bS0NLCHc5 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit On Fri, 13 Feb 2004 11:39:28 -0500 "JJB" <Barbish3@adelphia.net> probably wrote: > When an FBSD system crooks, and It reboots it's self, very seldom > does any of issued problem messages have time to be posted > completely before the rug is pulled out from under the log write > process by the reboot occurring. All you can find out from the logs > is yes indeed it did reboot. You are SOL, just like the rest of us > when this happens to us. Probably a loose chance, but `last' could come up with something... Anyway it still just reads the logs... If you're afraid this may happen again, and you're on a network, you might want to use the remote logging feature of syslog. Then, all messages will make it to the destination, right up to the reboot. HTH, -- DoubleF Truth is the most valuable thing we have -- so let us economize it. -- Mark Twain --Signature=_Sat__14_Feb_2004_17_10_54_+0300_SlvrNU.bS0NLCHc5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFALix6wo7hT/9lVdwRAusMAJ4t8RVhyLPzfFaoBoMIkAIc1GZvGwCeOXSL loSkIwbTNbw0eC3gBfMjk5M= =NPng -----END PGP SIGNATURE----- --Signature=_Sat__14_Feb_2004_17_10_54_+0300_SlvrNU.bS0NLCHc5--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040214171054.10e8f6ba>