CVS log for src/usr.sbin/envstat/config.c

Up to [cvs.NetBSD.org] / src / usr.sbin / envstat

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

envstat: remove redundant local variables

This fixes the lint warnings about "effectively discards 'const'".

No binary change.

For raw output (-x) allow to extract individual properties like drvctl -p.
E.g.

# envstat -x /vcmbox0/0/cur-value
328150000

Update for proplib(3) API changes.

Use __dead

Catchup with rmind-uvmplock merge.

Instead of relying on the want-percent attribute, use the sensor
type to restrict value-based limits from Battery-capacity sensors.

Apply proper conversion (which is _no_ conversion) when setting limit
values for sensors of type ENVSYS_INTEGER.

Update userland envstat(8) to handle new {high,maximum}-capacity limits.

Sync with wrstuden-revivesa-base-2.

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@

sync with HEAD

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.

sync with HEAD

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.

sync with HEAD

file config.c was added on branch matt-armv6 on 2007-11-06 23:36:23 +0000

- 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.

Fix a typo that prevented a 'critical-capacity' property to
be added.

If a critical-capacity property is found, make sure that the
'monitoring-supported' object is true.

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.

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.