Datasheet

“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 371 — #397
i
i
i
i
i
i
i
i
17
Power Management
Make sure that the following standard options for the correct processing of
suspend, standby, occurrence, and resume are set (normally, these are the
default settings following the installation of SUSE LINUX):
POWERSAVE_EVENT_GLOBAL_SUSPEND="prepare_suspend"
POWERSAVE_EVENT_GLOBAL_STANDBY="prepare_standby"
POWERSAVE_EVENT_GLOBAL_RESUME_SUSPEND="restore_after_suspend"
POWERSAVE_EVENT_GLOBAL_RESUME_STANDBY="restore_after_standby"
In /etc/powersave.conf (configuration file of the powersave dae-
mon), these events are allocated to the powersave_proxy script. This
script is executed when these events occur (default setting following the
installation):
global.suspend=/usr/sbin/powersave_proxy
global.standby=/usr/sbin/powersave_proxy
global.resume.suspend=/usr/sbin/powersave_proxy
global.resume.standby=/usr/sbin/powersave_proxy
Custom Battery States
In the file /etc/powersave.conf, define three battery charge levels (in
percent) that trigger system alerts or execute specific actions when they are
reached.
POWERSAVED_BATTERY_WARNING=20
POWERSAVED_BATTERY_LOW=10
POWERSAVED_BATTERY_CRITICAL=5
The actions or scripts to execute when the charge levels drops under the
specified limits are defined in /etc/powersave.conf. The action type is
configured in /etc/sysconfig/powersave/common:
POWERSAVE_EVENT_BATTERY_NORMAL="ignore"
POWERSAVE_EVENT_BATTERY_WARNING="notify"
POWERSAVE_EVENT_BATTERY_LOW="notify"
POWERSAVE_EVENT_BATTERY_CRITICAL="suspend"
Further options are explained in this configuration file.
371
SUSE LINUX Enterprise Server