On Sat, 8 Nov 2008, Joerg Sonnenberger wrote:
On Sat, Nov 08, 2008 at 11:57:19AM -0800, Paul Goyette wrote:As long as you get a dmesg and console entry for the critical-over case, I don't care where it gets handled. So envsys would be prefered for this.You won't get a dmesg unless we leave the aprint_*() calls. Normally, you only get syslog/console messages from sysmon_envsys when a monitored sensor generates an event.Well, critical temperature is one of those things that should be logged, if you still have a change to log it off somewhere before the machine is forcefully powered off.
Yes, powerd's /etc/power/scripts/sensor_temperature will syslog the event by default. Depending on your /etc/syslogd.conf file, that may include logging the event on a remote host. This is at least as persistent as dmesg/aprint_*() which may or may not be saved in NVRAM across any power-down that may be invoked.
---------------------------------------------------------------------- | Paul Goyette | PGP DSS Key fingerprint: | E-mail addresses: | | Customer Service | FA29 0E3B 35AF E8AE 6651 | paul%whooppee.com@localhost | | Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette%juniper.net@localhost | ----------------------------------------------------------------------