On Mon, Dec 8, 2014 at 3:37 PM, trondd <tro...@gmail.com> wrote: > On Mon, Dec 8, 2014 at 3:23 PM, trondd <tro...@gmail.com> wrote: >> On Mon, Dec 8, 2014 at 11:47 AM, David Higgs <hig...@gmail.com> 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 indicators that you consider in >>> "good" state when On (i.e. ACPresent). >>> >> >> Isn't saying high=0 kind of the same thing as saying low=1? > > > Oh, I think I get this. Since the sensor doesn't trigger if it is on the > limit, only outside the limit, you have to set up which is the OK state. > > Still a little confusing but I guess there is no way to automatically know > if an indicator is supposed to be Off or On when it's in it's good state? >
Kind of. The high/low difference is what values you consider "within" normal operating parameters (and the output of %l). The upd(4) code hasn't yet been taught how to map specific indicator values to OK / WARN / CRITICAL status. Currently any value successfully read is marked OK. I'm working with tech@ and slowly writing diffs to improve these things. --david
