From owner-cvs-all@FreeBSD.ORG Mon Feb 2 12:52:49 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA2F216A4CE; Mon, 2 Feb 2004 12:52:49 -0800 (PST) Received: from mail.lambertfam.org (www.lambertfam.org [216.223.208.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7377043D62; Mon, 2 Feb 2004 12:52:48 -0800 (PST) (envelope-from lambert@lambertfam.org) Received: from localhost (localhost [127.0.0.1]) by mail.lambertfam.org (Postfix) with ESMTP id A63E634D73; Mon, 2 Feb 2004 15:52:47 -0500 (EST) Received: from mail.lambertfam.org ([127.0.0.1]) by localhost (www.lambertfam.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50289-10; Mon, 2 Feb 2004 15:52:46 -0500 (EST) Received: from laptop.lambertfam.org (unknown [216.223.208.56]) by mail.lambertfam.org (Postfix) with ESMTP id A0F7834D70; Mon, 2 Feb 2004 15:52:46 -0500 (EST) Received: by laptop.lambertfam.org (Postfix, from userid 1001) id 9613CC136; Mon, 2 Feb 2004 15:52:46 -0500 (EST) Date: Mon, 2 Feb 2004 15:52:46 -0500 From: Scott Lambert To: Scott Long Message-ID: <20040202205246.GB742@laptop.lambertfam.org> References: <200402021803.i12I3ZJW016336@repoman.freebsd.org> <20040202122040.A30296@pooker.samsco.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040202122040.A30296@pooker.samsco.home> User-Agent: Mutt/1.5.5.1i X-Virus-Scanned: by amavisd-new at lambertfam.org cc: cvs-src@FreeBSD.org cc: Nate Lawson cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/acpica acpi_thermal.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 20:52:50 -0000 On Mon, Feb 02, 2004 at 12:22:36PM -0700, Scott Long wrote: > > Are there any provisions for putting something in the syslog before the > shutdown? At least a series of warnings to the console well before the > shutdown happens would be a good thing. Making sure that those warnings > get fsynced to disk would be even more ideal. But just a spontaneous > shutdown is not terribly helpful. The single critical warning log message was successfully fsynced in my case. -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org