From owner-acpi-jp@jp.freebsd.org  Thu Sep 27 21:28:32 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id VAA59364;
	Thu, 27 Sep 2001 21:28:32 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from acampi.inet.it ([213.92.1.165])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id VAA59358
	for <acpi-jp@jp.freebsd.org>; Thu, 27 Sep 2001 21:28:30 +0900 (JST)
	(envelope-from andrea@acampi.inet.it)
Received: by acampi.inet.it (Postfix, from userid 1000)
	id 2694E155DA; Thu, 27 Sep 2001 14:28:27 +0200 (CEST)
Date: Thu, 27 Sep 2001 14:28:27 +0200
From: Andrea Campi <andrea@webcom.it>
To: acpi-jp@jp.freebsd.org
Message-ID: <20010927142827.A81488@webcom.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.22.1i
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+010328
X-Sequence: acpi-jp 1305
Subject: [acpi-jp 1305] acpi_tz0 logging
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: andrea@webcom.it

Hi folks,

do we really have to log acpi_tz0 messages (temperature >= setpoint and such)
at kern.crit level? On my laptop (Thinkpad 570E) they start appearing as soon
as I compile anything, or do anything else processor- or disk- intensive. I
know I could configure syslogd not to send these to the console, but then I
might risk losing some real critical messages.

Bye,
	Andrea
