summaryrefslogtreecommitdiffstats
path: root/usr.sbin/sensorsd/sensorsd.8 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Adjust references for sysctl(3) to sysctl(2)deraadt2018-01-121-4/+4
|
* Text improvements for precision and clarity, in particular properlyschwarze2017-07-231-13/+20
| | | | | | | | | 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@
* Add command line option -f to specify alternative config file.bluhm2017-03-201-2/+8
| | | | from Matthias Pitzl
* use file system path (.Pa) semantic markup macros where appropriate.sobrado2015-07-271-3/+3
| | | | ok jmc@
* Don't single out ami(4) here; other RAID drivers support logicalmillert2014-08-261-5/+3
| | | | drive reporting too. OK jsing@
* text simplification;jmc2008-03-161-2/+2
|
* Reduce the number of unnecessary time(3)/gettimeofday(2) calls, and make surecnst2008-03-161-8/+6
| | | | | | | | | | | that the time always goes forward, so reports are neither duplicated nor lost. Report state changes stabilised through dampening immediately, instead of delay- ing them until the next reporting window; previously, it was common for check() to lag one second behind report(), hence the initial report was delayed one extra minute (this then reduces the number of sleep(3)/nanosleep(2) calls, too). ok ckuethe; some man-page suggestions jmc
* sort options list;jmc2007-11-281-5/+5
|
* add options to specify the check and report intervals. ok deraadttedu2007-11-281-2/+12
|
* add caveats section, documenting previously undocumented state dumping mechanism; ok jmc@ henning@cnst2007-08-111-1/+12
|
* s/ and alerter// against previous: 'alerter' is not a standard word (yet),cnst2007-08-111-3/+3
| | | | | even if it is present in certain dictionaries (it is). Also, it doesn't add that much to .Nd anyhow. Requested by jmc@
* sync sensorsd.8: add my copyright; change NAME summary; fix some grammar;cnst2007-08-101-7/+16
| | | | | | | fix description of when the command is executed (it was wrong from the start); say a few more words about automatic monitoring of all sensors that keep state. ok henning@
* something went wrong w/ previous;jmc2007-07-311-2/+2
|
* document the -d option of sensorsd; input and ok from jmc@, deraadt@robert2007-07-311-2/+12
|
* convert to new .Dd format;jmc2007-05-311-2/+2
|
* Major update to sensorsd.cnst2007-05-301-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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@
* ami sysctl diff; from michael knudsenjmc2006-04-211-3/+5
| | | | ok dlg
* remove drivers from here.aanriot2005-08-101-7/+1
| | | | ok jsg@ deraadt@
* add lmtemp(4) and viasio(4).aanriot2005-08-101-1/+3
| | | | ok grange@
* document conf file reload w/ SIGHUP;jmc2005-05-111-1/+3
| | | | | from michael knudsen; ok henning@
* sensorsd(8) execute command on exceeding limitshshoexer2005-04-011-5/+6
| | | | | | from matthew.gream@pobox.com, thanks! cleaning and ok deraadt@
* add reference to nsclpcsio(4) to SEE ALSO;jmc2004-06-271-2/+3
| | | | prodded by Alexey E. Suslikov;
* FILES /etc/sensorsd.confhenning2003-10-071-1/+7
| | | | | spotted by millert@ ok millert@ jmc@
* .Xr it 4henning2003-10-061-1/+2
| | | | PR3512, From: zejames@greyhats.org
* sensorsd monitors the hardware sensors as reported by sysctl in hw.sensors.henning2003-09-241-0/+49
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
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.