On 26 February 2016 at 08:40, lilit-aibolit wrote:
> I've tried to change low=1:high=2 to low=0:high=0
> but I haven't got *Off* current state for this sensor from sensord:
>
> - hw.sensors.upd0.indicator2=On (ACPresent), OK
>
> Even for AC disconnected sensord repors that ACPresent is *On*,
> how
I've tried to change low=1:high=2 to low=0:high=0
but I haven't got *Off* current state for this sensor from sensord:
- hw.sensors.upd0.indicator2=On (ACPresent), OK
Even for AC disconnected sensord repors that ACPresent is *On*,
however when I look for
- sysctl hw.sensors.upd0.indicator2
it r
Hi list, why I don't have extra line in output with sensor
upd0.percent1(RemainingCapacity)?
Is it related to model of my UPS?
# usbdevs | grep UPS
addr 4: Back-UPS ES 525 FW:851.t3.I USB FW:t3, American Power Conversion
# sysctl hw.sensors
hw.sensors.upd0.indicator0=Off (Charging), OK
hw.sen
On 19 October 2015 at 11:31, David Higgs wrote:
> On Mon, Oct 19, 2015 at 11:11 AM, Maxim Khitrov wrote:
>> Also, upd always sets sensor status to "OK," so sensorsd never
>> triggers commands for status changes; we have to use low/high limits
>> until this is fixed. One proposed hack was to use "
On Mon, Oct 19, 2015 at 2:31 PM, David Higgs wrote:
> On Mon, Oct 19, 2015 at 11:11 AM, Maxim Khitrov wrote:
>>
>> On Mon, Dec 8, 2014 at 3:45 PM, David Higgs wrote:
>> > On Mon, Dec 8, 2014 at 3:37 PM, trondd wrote:
>> >> On Mon, Dec 8, 2014 at 3:23 PM, trondd wrote:
>> >>> On Mon, Dec 8, 201
On Mon, Oct 19, 2015 at 11:11 AM, Maxim Khitrov wrote:
> On Mon, Dec 8, 2014 at 3:45 PM, David Higgs wrote:
> > On Mon, Dec 8, 2014 at 3:37 PM, trondd wrote:
> >> On Mon, Dec 8, 2014 at 3:23 PM, trondd wrote:
> >>> On Mon, Dec 8, 2014 at 11:47 AM, David Higgs wrote:
>
>
> sysct
On Mon, Dec 8, 2014 at 3:45 PM, David Higgs wrote:
> On Mon, Dec 8, 2014 at 3:37 PM, trondd wrote:
>> On Mon, Dec 8, 2014 at 3:23 PM, trondd wrote:
>>> On Mon, Dec 8, 2014 at 11:47 AM, David Higgs wrote:
sysctl(8) will display Off if the value is zero, and On for nonzero.
So
On Mon, Dec 8, 2014 at 3:45 PM, David Higgs wrote:
> I'm working with tech@ and slowly writing diffs to improve these things.
>
> --david
>
I saw that. Thanks!
Tim.
On Mon, Dec 8, 2014 at 3:37 PM, trondd wrote:
> On Mon, Dec 8, 2014 at 3:23 PM, trondd wrote:
>> On Mon, Dec 8, 2014 at 11:47 AM, David Higgs wrote:
>>>
>>>
>>> sysctl(8) will display Off if the value is zero, and On for nonzero.
>>> So, using the "closed interval" rule above, you should use "hi
On Mon, Dec 8, 2014 at 3:23 PM, trondd wrote:
> On Mon, Dec 8, 2014 at 11:47 AM, David Higgs wrote:
>
>>
>> sysctl(8) will display Off if the value is zero, and On for nonzero.
>> So, using the "closed interval" rule above, you should use "high=0"
>> for indicators that you consider in "good" st
On Mon, Dec 8, 2014 at 11:47 AM, David Higgs wrote:
>
> sysctl(8) will display Off if the value is zero, and On for nonzero.
> So, using the "closed interval" rule above, you should use "high=0"
> for indicators that you consider in "good" state when Off (i.e.
> ShutdownImminent), and "low=1" for
On Sun, Nov 30, 2014 at 10:54 AM, Marcus MERIGHI wrote:
> for the impatient, here are my questions:
>
> - Although I use the same (undocumented, undeadly.org) trick of
> "low=1:high=2" for indicators everywhere, this can result in
> "On is below On", and "Off is below On"
> - Although I use "l
for the impatient, here are my questions:
- Although I use the same (undocumented, undeadly.org) trick of
"low=1:high=2" for indicators everywhere, this can result in
"On is below On", and "Off is below On"
- Although I use "low=1:high=2", I get "On" for %3 (low limit) as well
as for %4 (hig
hig...@gmail.com (David Higgs), 2014.11.28 (Fri) 15:43 (CET):
> On Fri, Nov 28, 2014 at 2:45 AM, Marcus MERIGHI wrote:
> > What I have now:
> >
> > $ getcap -a -f /etc/sensorsd.conf
> > hw.sensors.upd0.indicator0:low=1:high=2:command=/etc/sensorsd/upd.sh \
> > %l %n %s %x %t %2 %3 %4
> > hw.sensor
On Fri, November 28, 2014 9:43 am, David Higgs wrote:
> On Fri, Nov 28, 2014 at 2:45 AM, Marcus MERIGHI
> wrote:
>> What I have now:
>>
>> $ getcap -a -f /etc/sensorsd.conf
>> hw.sensors.upd0.indicator0:low=1:high=2:command=/etc/sensorsd/upd.sh \
>> %l %n %s %x %t %2 %3 %4
>> hw.sensors.upd0.indic
On Fri, November 28, 2014 2:45 am, Marcus MERIGHI wrote:
> j...@entropicblur.com (Joe Gidi), 2014.11.27 (Thu) 16:41 (CET):
>> I just spent some more time poking at this and I'm still unable to get
>
> So did I...
>
>> sensorsd to recognize upd state changes. This is a bit of a frustrating
>> regres
nal Message-
> From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of
> David Higgs
> Sent: Friday, November 28, 2014 9:43 AM
> To: misc@openbsd.org
> Subject: Re: sensorsd, upd, and state changes
>
> Do you mind saying what type of USB you have, and wh
On Fri, Nov 28, 2014 at 2:45 AM, Marcus MERIGHI wrote:
> What I have now:
>
> $ getcap -a -f /etc/sensorsd.conf
> hw.sensors.upd0.indicator0:low=1:high=2:command=/etc/sensorsd/upd.sh \
> %l %n %s %x %t %2 %3 %4
> hw.sensors.upd0.indicator1:low=1:high=2:command=/etc/sensorsd/upd.sh \
> %l %n %s %x
j...@entropicblur.com (Joe Gidi), 2014.11.27 (Thu) 16:41 (CET):
> I just spent some more time poking at this and I'm still unable to get
So did I...
> sensorsd to recognize upd state changes. This is a bit of a frustrating
> regression from my point of view, since I can no longer use apcupsd unle
I just spent some more time poking at this and I'm still unable to get
sensorsd to recognize upd state changes. This is a bit of a frustrating
regression from my point of view, since I can no longer use apcupsd unless
I disable uhidev in the kernel.
Does anyone have a working example configuration
On Sun, November 23, 2014 11:51 am, Marcus MERIGHI wrote:
> j...@entropicblur.com (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 t
j...@entropicblur.com (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[
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 mic
Hi Marcus,
Thanks for the reply. Unfortunately, the "low=1:high=2" doesn't seem to
work for indicator2. When I start sensorsd I see an initial event logged
as the status goes from undefined to OK, but no further events as I
unplug/plug the UPS. I tried monitoring indicator0 as in the Undeadly
exam
j...@entropicblur.com (Joe Gidi), 2014.11.23 (Sun) 01:22 (CET):
> I'm running OpenBSD 5.6/amd64 on my fileserver. It has an APC UPS that was
> previously managed with apcupsd. Since I upgraded to 5.6, the UPS now
> attaches as a upd device:
>
> $ dmesg | grep uhidev3
> uhidev3 at uhub3 port 5 conf
25 matches
Mail list logo
