## Path:        	System/Powermanagement/Powersave/Events
## Description: In this section you can define what actions to perform \
## if a powersaved event occurs. Read the documentation in \
## /usr/share/doc/packages/powersave/ for more informations on how to \
## add customized actions. You can specify multiple actions for a given \
## event, just separate them with whitespace.\n \
## Note: Your system might not generate all of the events.

## Path:        	System/Powermanagement/Powersave/Events
## Type:        	string
# Events executed at daemon start.
EVENT_DAEMON_START="ignore"

## Path:        	System/Powermanagement/Powersave/Events
## Type:        	string
# Events executed at a scheme change. The scheme change event is also thrown
# if the machine is e.g. unplugged from AC or the daemon is started.
EVENT_DAEMON_SCHEME_CHANGE="set_disk_settings"

## Path:        	System/Powermanagement/Powersave/Events
## Type:        	string
#
# What events should be processed if the
# powersave daemon terminates?
EVENT_DAEMON_TERMINATE="dethrottle"

## Path:        	System/Powermanagement/Powersave/Events
## Type:        	string
EVENT_ACADAPTER_ONLINE="reread_cpu_capabilities"
EVENT_ACADAPTER_OFFLINE="reread_cpu_capabilities"

## Path:        	System/Powermanagement/Powersave/Events
## Type:        	string(notify,wm_shutdown,wm_logout,standby,suspend_to_ram,suspend_disk,screen_saver,ignore)
#
# The specified values(actions) will take effect, when the 
# battery state changes from "normal" to "warning".
EVENT_BATTERY_WARNING="notify"

## Path:        	System/Powermanagement/Powersave/Events
## Type:        	string(notify,wm_shutdown,wm_logout,standby,suspend_to_disk,suspend_to_ram,screen_saver,ignore)
#
# The specified values(actions) will take effect, when the 
# battery state changes from "warning" to "low".
EVENT_BATTERY_LOW="notify"

## Path:        	System/Powermanagement/Powersave/Events
## Type:        	string(notify,wm_shutdown,wm_logout,standby,suspend_to_disk,suspend_to_ram,screen_saver,ignore)
#
# The specified values(actions) will take effect, when the 
# battery state changes from "low" to "critical".
EVENT_BATTERY_CRITICAL="wm_shutdown"

# This event is never reached
EVENT_BATTERY_NORMAL="ignore"

## Path:        	System/Powermanagement/Powersave/Events
## Type:        	string(notify,wm_shutdown,wm_logout,standby,suspend_to_disk,suspend_to_ram,screen_saver,switch_vt,ignore)
#
# Button events. What functions of the proxy should be
# triggered if a ACPI button is pressed?
#
# Hint: switch_vt could be useful for the LID_OPEN event (replace ignore)
# some graphic cards might need switching to a virtual terminal
# and back to let the X-server recover properly
EVENT_BUTTON_POWER="wm_shutdown"
EVENT_BUTTON_SLEEP="suspend_to_disk"
EVENT_BUTTON_LID_OPEN="ignore"
EVENT_BUTTON_LID_CLOSED="screen_saver"

## Path:        	System/Powermanagement/Powersave/Events
## Type:        	string
#
# Gets processed if the powersave tool requests
# a CPU frequency policy change. (e.g. powersave --performance)
# These values are thought for later enhancements.
# You may want to get your own function invoked to enable advanced
# power saving functionalities.
# However it would be easier to modify the binary that should
# be invoked for the event in /etc/powersave.conf.
EVENT_PROCESSOR_PERFORMANCE="ignore"
EVENT_PROCESSOR_POWERSAVE="ignore"
EVENT_PROCESSOR_DYNAMIC="ignore"

## Path:        	System/Powermanagement/Powersave/Events
## Type:		list(notify,wm_shutdown,wm_logout,standby,suspend_to_disk,suspend_to_ram,power_off,screen_saver)
#
# What should happen if a temperature limit is reached?
EVENT_TEMPERATURE_CRITICAL="notify"
EVENT_TEMPERATURE_HOT="notify"
EVENT_TEMPERATURE_PASSIVE="ignore"
EVENT_TEMPERATURE_ACTIVE="ignore"
EVENT_TEMPERATURE_OK="ignore"

## Path:        	System/Powermanagement/Powersave/Events
## Type:        	string
#
# This event gets thrown if a unknown event is encountered by the daemon.
# Unknown events include e.g. ACPI hotkeys on some machines.
# A description of this mechanism is available in
# /usr/share/doc/packages/powersave/README.events.
EVENT_OTHER="hotkey_handler"

## Path:        	System/Powermanagement/Powersave/Events
## Type:        	string
#
# The kernel may inform that changes on CPU frequencies or throttling
# states capabilites have been taken place.
# In this case a cpu_notify event is generated by the powersave daemon and
# the internal function reread_cpu_capabilities should be processed
EVENT_PROCESSOR_NOTIFY="reread_cpu_capabilities"

## Path:        	System/Powermanagement/Powersave/Events
## Type:        	string
#
# After the processor is idle (CPU_LOW) for a specific time
# see a processor.idle event is thrown.
# If the cpu usage goes beyond the CPU_HIGH value
# a processor.busy event is thrown at once.
# There will never be one event thrown twice in a row, they 
# alternate! This is a perfect place to add additional
# power saving functionalities.
EVENT_PROCESSOR_BUSY="dethrottle"
EVENT_PROCESSOR_IDLE="throttle"

## Path:        	System/Powermanagement/Powersave/Events
## Type:        	string
#
# The specified functions that get processed
# when an suspend/standby is requested should not be modified.
# See System/Powermanagement/Powersave/Suspend or Standby
# for possible modifications if you encounter problems
# with these.
# You should change those only if you know what you are doing,
# if you remove e.g. the "screen_saver" event here, graphical
# clients like kpowersave will no longer lock the screen on
# suspend, no matter what. You have been warned :-)
EVENT_GLOBAL_SUSPEND2DISK="prepare_suspend_to_disk screen_saver do_suspend_to_disk"
EVENT_GLOBAL_SUSPEND2RAM="prepare_suspend_to_ram screen_saver do_suspend_to_ram"
EVENT_GLOBAL_STANDBY="prepare_standby screen_saver do_standby"

EVENT_GLOBAL_RESUME_SUSPEND2DISK="restore_after_suspend_to_disk"
EVENT_GLOBAL_RESUME_SUSPEND2RAM="restore_after_suspend_to_ram"
EVENT_GLOBAL_RESUME_STANDBY="restore_after_standby"

## Path:        	System/Powermanagement/Powersave/Events
## Type:        	string
#
# This event gets executed on suspend to disk if a suspend2
# enabled kernel is found (/proc/suspend2 exists)
EVENT_GLOBAL_SUSPEND2DISK_OTHER="suspend2"
