POWERD(8) | System Manager's Manual | POWERD(8) |
powerd
— power
management daemon for sysmon
powerd |
[-dn ] |
powerd
acts upon power management events
posted by the kernel's power management facility. When events are posted,
powerd
translates the event into a script name and a
list of arguments. powerd
then runs the script in
order to implement the power management policy defined by the system
administrator.
The following options are available:
All configuration of powerd
is
encapsulated into scripts that are run when power management events occur.
The daemon will look for the scripts from the directory
/etc/powerd/scripts.
Configuration scripts are run synchronously;
powerd
will start the script and wait for its
completion before it handles the next event.
Configuration scripts are called with different arguments, depending on the script class. These classes are described in the following sections.
Power switch scripts are called when a state change event occurs on a power switch device. Power switch scripts are called with two arguments: the device with which the event is associated, and the event type.
The following power switch script names are defined:
The following events are defined for power switch devices:
The following is an example of how a power button script might be invoked when a power button is pressed by the operator:
/etc/powerd/scripts/power_button acpibut0 pressed
envsys(4) scripts are called when a condition was triggered in a sensor. These scripts are called with three arguments: the device associated, the event type, and the sensor's name. The sensor_drive and the sensor_battery scripts uses a fourth argument: state description.
The following envsys script names are defined:
The following events are defined for fan, indicator, power, resistance, temperature, and voltage sensors:
The following event is defined for all scripts, but it is only sent if any of the previous events has been previously sent:
The following events are defined only for battery sensors:
The following events are defined for drive and battery sensors:
The following is an example of how a temperature sensor script might be invoked when a critical over condition is triggered:
/etc/powerd/scripts/sensor_temperature lm0 critical-over "CPU Temp"
acpi(4), acpiacad(4), acpibut(4), acpilid(4), envsys(4), i386/apm(4)
powerd
first appeared in
NetBSD 2.0. Support to handle
envsys(4) events appeared in
NetBSD 5.0.
powerd
was written by
Jason R. Thorpe
⟨thorpej@wasabisystems.com⟩ and contributed by Wasabi Systems,
Inc.
Juan Romero Pardines added support to handle
envsys(4) events.
Due to its synchronous nature powerd
cannot be trusted to handle events within a certain time.
December 15, 2010 | NetBSD 10.99 |