From owner-freebsd-questions@FreeBSD.ORG Sat Feb 14 06:07:34 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3860816A4CE for ; Sat, 14 Feb 2004 06:07:34 -0800 (PST) Received: from mx.tele-kom.ru (mx.tele-kom.ru [213.80.148.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 1080F43D1D for ; Sat, 14 Feb 2004 06:07:33 -0800 (PST) (envelope-from doublef@tele-kom.ru) Received: (qmail 73199 invoked by uid 555); 14 Feb 2004 17:07:31 +0300 Received: from hal.localdomain (213.80.149.223) by t-k.ru with TeleMail/2 id 1076767647-73179 for barbish3@adelphia.net; Sat, 14 Feb 17:07:27 2004 +0300 (MSK) Date: Sat, 14 Feb 2004 17:10:54 +0300 From: Sergey 'DoubleF' Zaharchenko To: Barbish3@adelphia.net Message-Id: <20040214171054.10e8f6ba@Hal.localdomain> In-Reply-To: References: <20040213155654.64692.qmail@web40606.mail.yahoo.com> X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i386-portbld-freebsd4.8) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Sat__14_Feb_2004_17_10_54_+0300_SlvrNU.bS0NLCHc5" cc: freebsd-questions@freebsd.org cc: John DeStefano Subject: Re: reboot record information X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Feb 2004 14:07:34 -0000 --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" 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--