An embedded and charset-unspecified text was scrubbed... Name: warning1.txt Url: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20040928/b5347961/attachment.txt -------------- next part -------------- > > By the way, why are there no shutdown options in sensord? > > Sensord is abandonware. It's that easy. None of us developers use it. Ah, that would explain a few things. Guess I'll shut it off then until I get enough time to see what state it's really in. > > > sensord does pretty much everything mondo does except give > > an option for shutdown. Is this feature going to be added to > > sensord anytime soon? > > Patches are welcome ;) > > > Failing that, what is the most common "shut down on over temperature" > > script/program in use with lm_sensors on 2.6.x kernels? > > No idea, sorry. > Turned out not to be too difficult to roll my own. One of the attached two files use my "extract" program ftp://saf.bio.caltech.edu/pub/software/linux_or_unix_tools/extract.c and lm_sensors and that's pretty much it to monitor CPU T and Fan speeds, with a final poweroff if a value gets too badly out of range, logs and warnings otherwise. [For Unix purists extract could be eliminated and replaced with sed, set, awk or the like, but it's my Swiss army knife program and builds and runs on every OS I've tried so far, so I tend to use it a lot.] sensor_monitor is the /etc/rc.d/init.d script and should work as is on Mandrake, RedHat, and other similar systems. sensor_monitor.sh is the daemon script, mine lives in /usr/local/sbin When running it doesn't go above .3% CPU, and then only once every 5 seconds, so the load is negligible. Regards, David Mathog mathog at caltech.edu Manager, Sequence Analysis Facility, Biology Division, Caltech -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/octet-stream Size: 2063 bytes Desc: not available Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20040928/b5347961/attachment.obj
