On Sun, November 23, 2014 11:51 am, Marcus MERIGHI wrote: > [email protected] (Joe Gidi), 2014.11.23 (Sun) 17:19 (CET): >> Just after I sent this, I happened to notice these lines in >> /var/log/messages. These came from the tests with the "low=1:high=2" >> attributes set in sensorsd.conf per the Undeadly example. >> >> Nov 23 10:58:08 microserver sensorsd[6250]: upd0.indicator2: exceeds >> limits: On is below On >> Nov 23 10:59:54 microserver sensorsd[12047]: upd0.indicator2: exceeds >> limits: On is below On >> Nov 23 11:07:00 microserver sensorsd[27413]: upd0.indicator0: exceeds >> limits: On is below On > > As I had just copied the undeadly example as-is to my sensorsd.conf I > did receive the e-mail (i.e. command= worked). It was a false positive, > though, as no one had pulled the plug. Did you really pull the plug or > was yours a false positive, too? > > Bye, Marcus
I actually tested by pulling the plug. In my testing, sensorsd detects a change and invokes my script when the daemon is first started; I believe this is because the status of the sensor goes from undefined to OK. However, after that, unplugging/plugging the UPS doesn't have any effect on sensorsd. Thanks, Joe
