summaryrefslogtreecommitdiffstats
path: root/usr.sbin/sensorsd (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* 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
|
* various grammar/text improvements;jmc2007-06-051-18/+18
|
* Convert sensorsd to use two-level data-structures. This makes sensorsd becnst2007-06-011-60/+115
| | | | | | | | more consistent with the current sensors framework, conserves some memory, and will make it easier to implement hotplugging and other nifty features in the future. This does not change any other functionality ATM. OK henning@, beck@.
* convert to new .Dd format;jmc2007-05-312-4/+4
|
* Major update to sensorsd.cnst2007-05-303-55/+155
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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@
* Remove watch_cnt in preparation for my bigger patch that makes sensorsdcnst2007-05-291-21/+8
| | | | | | | | | usable by default, where we will monitor all sensors that automatically provide status, and this watch_cnt won't make much sense. Besides, upon startup, sensorsd already shows all sensors that it is going to monitor, making this watch_cnt rather unimportant. ok henning@
* tweaks; help/ok cnstjmc2007-05-291-9/+9
|
* for sensorsd.conf entries, let's do matching by sensor type if maching by complete sysctl name does not yield anything; ok henning, ottocnst2007-05-292-21/+36
|
* do status dampening for OK status as well, i. e.henning2007-02-281-7/+3
| | | | | | | if a sensor is always bad, but sometimes goes OK for only a few seconds, we want to ignore that bogus change as well also fix setting if last_val. from Constantine, ok mickey
* add missing copyright; Constantinederaadt2007-02-231-1/+2
|
* increase buffer size; ie. for hw.sensors.ipmi0.indicator0deraadt2007-01-061-3/+4
| | | | from cnst+openbsd@bugmail.mojo.ru
* tweak;jmc2006-12-281-3/+3
|
* adapt to new two-level sensor sysctl framework; by Constantine A. Mureninderaadt2006-12-232-38/+74
|
* it appears some sensors flip duen to bugs or erroneous readings.mickey2006-12-181-12/+24
| | | | | | provide dampenning for negative events and simultaneously increase polling frequency accordingly to provide same rate of reporting. mbalmer@ beck@ deraadt@ ok
* sync printing w/ sysctl and also add missing sensor types to the conf parser; deraadt@ okmickey2006-09-161-6/+25
|
* wording;jmc2006-08-231-8/+9
|
* esm(4) also gives status (sometimes ;)mickey2006-08-231-4/+6
|
* allow monitoring sensors with their own status reporting such as ipmi or raid controllers; marco@ okmickey2006-08-232-17/+44
|
* ami sysctl diff; from michael knudsenjmc2006-04-211-3/+5
| | | | ok dlg
* when I initially hacked sensorsd, sensors started at hw.sensors.0 andhenning2006-04-011-2/+2
| | | | | | | there were no gaps ever. these days, we can have holes or start later. so on start scan 0..255 and do not abort if there's no entry, probe 'em all. found and analyzed by Sam Chill <samchill@gmail.com>, ok theo
* add two missing function declarationsdhill2006-03-201-8/+9
| | | | | | change sensor_status to sensorsd_status ok deraadt@
* beef up this file a little; ok grangejmc2006-03-071-14/+43
|
* don't error out but give a warning when sysctl()moritz2006-02-061-5/+4
| | | | | | fails with something else than ENOENT. suggested by tedu@ ok henning@
* When sysctl(3) fails, check for ENOENT instead of ENXIO to findmoritz2006-01-311-5/+10
| | | | | | the last sensor and don't monitor sensors, which are marked invalid. ok henning@
* 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@
* Support for SENSOR_INTEGER.jsg2005-08-041-1/+7
| | | | ok grange@, dlg@, henning@
* dlg did not test what he affects; enum clashderaadt2005-08-031-2/+2
|
* print negative values correctly; From: serge rasnikov <747500@gmail.com>henning2005-06-031-3/+3
|
* document conf file reload w/ SIGHUP;jmc2005-05-111-1/+3
| | | | | from michael knudsen; ok henning@
* spacingderaadt2005-04-211-3/+3
|
* fix buffer overrun introduced with my previous commit. Found and fixed byhshoexer2005-04-201-12/+11
| | | | | | moritz@; while around take care of snprintf return values help and ok moritz@, henning@
* new sentence, new line;jmc2005-04-021-4/+4
| | | | change an article;
* spacingderaadt2005-04-012-11/+8
|
* sensorsd(8) execute command on exceeding limitshshoexer2005-04-013-26/+132
| | | | | | from matthew.gream@pobox.com, thanks! cleaning and ok deraadt@
* ARGSUSED before signal handler with unused signoderaadt2004-09-141-2/+3
|
* add reference to nsclpcsio(4) to SEE ALSO;jmc2004-06-271-2/+3
| | | | prodded by Alexey E. Suslikov;
* Fix accidental busy loop waiting for a second to pass. Also, renameotto2004-04-111-7/+7
| | | | | | constants that defined a period of time. ok deraadt@ henning@
* add a default: case to the switch (sensor type) in the config file parserhenning2004-03-151-1/+4
| | | | | that just errs out if someone tries to configure limits for a sensor type we do not support, deraadt ok
* knf; jjy2+@pitt.eduderaadt2004-02-071-5/+6
|
* sync with sysctl/drivers + 0K == -273.15C; report grange; ok henningmarkus2004-01-081-3/+3
|
* reload is used in signal handler, make it volatile sig_atomic_thenning2003-12-221-3/+3
|
* 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
* sys/types.h is not really needed with sys/param.h.kevlo2003-10-011-2/+1
| | | | ok henning@
* o err out on start if no watches are definedhenning2003-09-301-7/+14
| | | | | o log how many watches are defined o on configuration reload also log how many watches we have
* set the log message ident with openlog(), ok henning@jose2003-09-301-1/+3
|
* uncomment daemon() call; spotted by jose@henning2003-09-291-3/+3
|
* sensorsd monitors the hardware sensors as reported by sysctl in hw.sensors.henning2003-09-244-0/+433
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.