defining the terms "sensor" and "alert", avoiding fuzzy wording
like "reporting period" and "state dumping", explaining how Boolean
values are represented and that ranges are inclusive, and mentioning
the syslog facility used. Also add relevant cross references and
drop irrelevant ones.
OK jmc@
and make it compatible with bsd.lv mandoc and with groff-1.21.
This tweak was originally added for compatibility with groff-1.15,
which is no longer needed.
ok jmc@ kristaps@
you might want to toggle an error light when a sensor is not OK. Perhaps
you might want to schedule a shutdown if a sensor is reporting bad news.
Now you can do this, and cancel that pending shutdown (or turn off the error
light) if the sensor decides all is well.
ok mbalmer (who came up with an almost identical diff months ago)
useful feedback and generally positive responses from deraadt, henning, msf
the impression that alerts are only issued when things go wrong, not when they
come back to specification -- but this was never the case with sensorsd.
Whilst here, also zip some useless examples, as we now have so many.
Discussed with jmc@
* add myself to the copyright; remove unneeded synopsis
* invalid sensors can now be monitored as such (since c2k7)
* manual boundaries for smart sensors are no longer ignored (since c2k7)
* populate history with 4.1 and 4.2 additions
* add caveats section documenting a long-standing misconception and a workaround
some help jmc@; ok jmc@
Improves support for both 'smart' (those providing sensor status) and
'old-style' sensors.
Due to re-design, the following improvements are now present and many
flaws are now gone:
== for smart sensors ==
* automatically monitor all sensors that provide status by themselves,
with the possibility to ignore certain individual sensors or sensors
of certain type (appropriate template for sensorsd.conf is included)
* report actual sensor status as provided by the driver. Previously,
WARN, CRITICAL and UNKNOWN statuses were considered the same, but
now they are different and will be reported separately. This also
improves readability of the log-files and consistency with sysctl
output.
* ability to ignore status provided by the driver with the 'istatus'
keyword ("ignore automatic status" or "I set the status"), with the
possibility to set your own settings for acceptable limits.
Previously, it was not possible to set any kind of user limits for
those sensors that had their own status facilities.
== for old-style sensors ==
* previously, lm(4)-style fans that were flagged SENSOR_FINVALID during
sensorsd startup were completely ignored, but now their invalid status
is appropriately reported, and they are monitored again when they come
out of their invalid mode
* previously, a sensor that had an empty entry in the configuration file
was reported to be "within limits", but now it will not be monitored
at all (unless, of cause, it provides its own status)
As a bonus, sensorsd syslog entries should now be shorter, and the
majority of them will fit on one line on 80-column terminals.
ok beck@, henning@, deraadt@
limits can be configured, out of range notifications through syslog.
config file parsing based on bob's hints, lots of hints from theo
feedback from grange, otto, mickey as well
ok deraadt@; grange@ on an earlier version
