On 2015-03-22, T. Ribbrock <emga...@gmx.net> wrote:
> What I cannot seem to get to work is that sensorsd *reacts* to these
> changes. Based on the examples in the thread mentioned above, I've
> created a small script "/etc/sensorsd/upd.sh" that looks as follows:
>
> # cat /etc/sensorsd/upd.sh
> echo "${@}" | logger -t UPD
>
> I have then created the following sensorsd.conf:
> hw.sensors.upd0.indicator0:high=0:command=/etc/sensorsd/upd.sh %x.%t%n
> Charging %2 %s
> hw.sensors.upd0.indicator1:high=0:command=/etc/sensorsd/upd.sh %x.%t%n
> Discharging %2 %s
> hw.sensors.upd0.indicator2:low=1:command=/etc/sensorsd/upd.sh %x.%t%n
> ACPresent %2 %s
> hw.sensors.upd0.indicator3:low=1:command=/etc/sensorsd/upd.sh %x.%t%n
> BatteryPresent %2 %s
> hw.sensors.upd0.indicator4:high=0:command=/etc/sensorsd/upd.sh %x.%t%n
> ShutdownImminent %2 %s
> hw.sensors.upd0.percent0:low=25:command=/etc/sensorsd/upd.sh %x.%t%n
> FullChargeCapacity %2 %s
> hw.sensors.upd0.percent1:low=25:command=/etc/sensorsd/upd.sh %x.%t%n
> RemainingCapacity %2 %s
It's a bit of a hack, but for the "normally on" sensors like ACPresent you can
use :low=1:high=2
http://www.undeadly.org/cgi?action=article&sid=20140320093943&pid=1
