Re: 4.8 sensorsd blind spot, failure to trigger command on any state changes after initialisation

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: mark hellewell
Date: Sunday, November 14, 2010 - 5:03 pm

On 14 November 2010 20:06, Constantine A. Murenin <mureninc@gmail.com>wrote:



Ah; thanks for your reply!  I think I was expecting the wrong thing from
sensorsd -- thanks for shedding light on what's going on.  I'll use a shell
script command on watthour3 to check the other vals through sysctl directly,
as you suggest.

I wish that hw.sensors.acpibat0.raw0 changed state from OK to something else
when it was discharging. I wonder why this isn't the case: CHARGING,
DISCHARGING, IDLE would be great additions I think.  Maybe it's done the way
it is for good reason.

Mark

C.
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: 4.8 sensorsd blind spot, failure to trigger command on ..., mark hellewell, (Sun Nov 14, 5:03 pm)