Date: Mon, 2 Feb 2004 12:54:36 -0800 (PST) From: Nate Lawson <nate@root.org> To: Scott Long <scottl@freebsd.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/acpica acpi_thermal.c Message-ID: <20040202124426.B23520@root.org> In-Reply-To: <20040202122040.A30296@pooker.samsco.home> References: <200402021803.i12I3ZJW016336@repoman.freebsd.org> <20040202122040.A30296@pooker.samsco.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2 Feb 2004, 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. I thought about this and will probably add notification to userland of a _CRT event via devd and then a default devd.conf entry that does "logger -t kern.emerg 'WARNING: critical temperature, shutting down in %d seconds'". This will happen on the 2nd to last _CRT event. It will go to all users via the default syslog.conf setting and will give them a little time to close apps. Currently, a message is printed right before shutting down but it only helps to know why the system suddenly shut down on you. Remember that typical temperatures for this shutdown are 90-100C (200-212F). This is not something you want to delay. If your system maintains that temperature over a period of 30 seconds, you want a shutdown. The parameters are specified by the system designer, who knows what the critical temperature is. -Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040202124426.B23520>