| History log of /src/usr.sbin/envstat/config.c |
| Revision | | Date | Author | Comments |
| 1.15 |
| 06-Oct-2024 |
rillig | envstat: remove redundant local variables
This fixes the lint warnings about "effectively discards 'const'".
No binary change.
|
| 1.14 |
| 14-Nov-2020 |
mlelstv | For raw output (-x) allow to extract individual properties like drvctl -p.
E.g.
# envstat -x /vcmbox0/0/cur-value
328150000
|
| 1.13 |
| 07-Jun-2020 |
thorpej | Update for proplib(3) API changes.
|
| 1.12 |
| 31-Aug-2011 |
joerg | Use __dead
|
| 1.11 |
| 08-Jun-2011 |
pgoyette | Instead of relying on the want-percent attribute, use the sensor
type to restrict value-based limits from Battery-capacity sensors.
|
| 1.10 |
| 05-Oct-2010 |
pgoyette | branches: 1.10.4;
Apply proper conversion (which is _no_ conversion) when setting limit
values for sensors of type ENVSYS_INTEGER.
|
| 1.9 |
| 15-Feb-2010 |
pgoyette | Update userland envstat(8) to handle new {high,maximum}-capacity limits.
|
| 1.8 |
| 22-Aug-2008 |
pgoyette | 1. provide for warning-min and warning-max alarm levels in addition to
critical-min and critical-max; also, a battery warning-capacity is
added in addition to a critical-capacity.
2. usr.sbin/envstat is modified to introduce a -W command line switch to
display the warning-* values instead of the critical-* values, and
envstat(8) and envsys.conf(5) man pages are updated appropriately.
3. Treat user-defined limits as a single continuum and generate a single
event regardless of how many boundaries a change in sensor value
crosses; ditto for driver-defined limits.
Fixes my PR/39021
Fixes my PR/39022
OK'd by christos@ bouyer@ cube@
|
| 1.7 |
| 02-Feb-2008 |
xtraeme | branches: 1.7.6;
Fix a bug in the 'refresh-timeout' device property that was giving
the same value to all devices even if the configuration file was
changed.
|
| 1.6 |
| 16-Nov-2007 |
xtraeme | Implement the 'refresh-timeout' property in device blocks for the
configuration files. This sets the timeout value that will be used
to check for critical limits.
The value can be viewed by the 'envstat -D' command.
|
| 1.5 |
| 09-Oct-2007 |
xtraeme | branches: 1.5.2;
- Do not allow a 'critical-{max,min}' property in battery
sensors (those that contain the 'want-percentage' object on its
dictionary), the 'critical-capacity' prop must be used instead.
- When setting a 'critical-{max,min}' property check if the value is
higher than the 'max-value' or lower than the 'min-value' on its
dictionary, raise an error if it's true.
|
| 1.4 |
| 09-Oct-2007 |
xtraeme | Fix a typo that prevented a 'critical-capacity' property to
be added.
|
| 1.3 |
| 07-Oct-2007 |
xtraeme | If a critical-capacity property is found, make sure that the
'monitoring-supported' object is true.
|
| 1.2 |
| 07-Oct-2007 |
xtraeme | Use two global dictionaries rather than only one:
- use one for temporary sensor dictionaries.
- use one as the dictionary that will be returned to send_dictionary().
This fixes multiple settings in multiple devices.
|
| 1.1 |
| 07-Oct-2007 |
xtraeme | New configuration file format for the envsys framework:
foo0 {
#
# CPU Temperature
#
sensor0 {
critical-max = 70C;
critical-min = 20C;
}
...
}
...
Removed the -m flag that was previously used to set properties for
sensors. Now the -c flag will process all properties specified in
the file (accepted as argument).
To remove all properties that were set, the new -S flag can be used.
This will restore default values for all devices.
|
| 1.5.2.4 |
| 23-Mar-2008 |
matt | sync with HEAD
|
| 1.5.2.3 |
| 09-Jan-2008 |
matt | sync with HEAD
|
| 1.5.2.2 |
| 06-Nov-2007 |
matt | sync with HEAD
|
| 1.5.2.1 |
| 09-Oct-2007 |
matt | file config.c was added on branch matt-armv6 on 2007-11-06 23:36:23 +0000
|
| 1.7.6.1 |
| 18-Sep-2008 |
wrstuden | Sync with wrstuden-revivesa-base-2.
|
| 1.10.4.1 |
| 23-Jun-2011 |
cherry | Catchup with rmind-uvmplock merge.
|
