Delay can be due to a limitations of sensorsd(8):
CAVEATS
Certain sensors may flip status from time to time. To guard against
false reports, sensorsd implements a state dumping mechanism. However,
this inevitably introduces an additional delay in status reporting and
command execution, e.g. one may notice that sensorsd makes its initial
report about the state of monitored sensors not immediately, but about 60
seconds after it is started.
Sergey Bronnikov
On Sun, Jan 19, 2014 at 10:34 PM, Laurence Rochfort
<[email protected]> wrote:
> Hello,
>
> I'm trying to use sensorsd to shutdown my Thinkpad T410 laptop when
> the battery reaches the "low capacity" level. However, when I add the
> line shown below to sensorsd.conf the laptop always shutdown within a
> couple of minutes of booting regardless of the current battery level
> or if running on AC power.
>
> The line I added to sensorsd.conf is:
>
> hw.sensors.acpibat0.amphour3:low=0.02Ah:command=/sbin/shutdown -hp now
>
> The sysctl output for my battery is:
>
> hw.sensors.acpibat0.volt0=10.80 VDC (voltage)
> hw.sensors.acpibat0.volt1=11.17 VDC (current voltage)
> hw.sensors.acpibat0.current0=0.99 A (rate)
> hw.sensors.acpibat0.amphour0=4.93 Ah (last full capacity)
> hw.sensors.acpibat0.amphour1=0.25 Ah (warning capacity)
> hw.sensors.acpibat0.amphour2=0.02 Ah (low capacity)
> hw.sensors.acpibat0.amphour3=0.27 Ah (remaining capacity), OK
> hw.sensors.acpibat0.raw0=2 (battery charging), OK
> hw.sensors.acpiac0.indicator0=On (power supply)
>
> Any suggestions as to what I'm doing wrong?
>
> Regards,
> Laurence.
