home *** CD-ROM | disk | FTP | other *** search
/ chilidog.highland.cc.ks.us / chilidog.highland.cc.ks.us.zip / chilidog.highland.cc.ks.us / backup / bradford.20101108.etc.tar.gz / bradford.20101108.etc.tar / etc / sysconfig / powersave / events < prev    next >
Text File  |  2007-02-24  |  6KB  |  150 lines
  1. ## Path:            System/Powermanagement/Powersave/Events
  2. ## Description: In this section you can define what actions to perform \
  3. ## if a powersaved event occurs. Read the documentation in \
  4. ## /usr/share/doc/packages/powersave/ for more informations on how to \
  5. ## add customized actions. You can specify multiple actions for a given \
  6. ## event, just separate them with whitespace.\n \
  7. ## Note: Your system might not generate all of the events.
  8. ## Path:            System/Powermanagement/Powersave/Events
  9. ## Type:            string
  10. # Events executed at daemon start.
  11. EVENT_DAEMON_START="ignore"
  12.  
  13. ## Path:            System/Powermanagement/Powersave/Events
  14. ## Type:            string
  15. # Events executed at a scheme change. The scheme change event is also thrown
  16. # if the machine is e.g. unplugged from AC or the daemon is started.
  17. EVENT_DAEMON_SCHEME_CHANGE="set_disk_settings"
  18.  
  19. ## Path:            System/Powermanagement/Powersave/Events
  20. ## Type:            string
  21. #
  22. # What events should be processed if the
  23. # powersave daemon terminates?
  24. EVENT_DAEMON_TERMINATE="dethrottle"
  25.  
  26. ## Path:            System/Powermanagement/Powersave/Events
  27. ## Type:            string
  28. EVENT_ACADAPTER_ONLINE="reread_cpu_capabilities"
  29. EVENT_ACADAPTER_OFFLINE="reread_cpu_capabilities"
  30.  
  31. ## Path:            System/Powermanagement/Powersave/Events
  32. ## Type:            string(notify,wm_shutdown,wm_logout,standby,suspend_to_ram,suspend_disk,screen_saver,ignore)
  33. #
  34. # The specified values(actions) will take effect, when the 
  35. # battery state changes from "normal" to "warning".
  36. EVENT_BATTERY_WARNING="notify"
  37.  
  38. ## Path:            System/Powermanagement/Powersave/Events
  39. ## Type:            string(notify,wm_shutdown,wm_logout,standby,suspend_to_disk,suspend_to_ram,screen_saver,ignore)
  40. #
  41. # The specified values(actions) will take effect, when the 
  42. # battery state changes from "warning" to "low".
  43. EVENT_BATTERY_LOW="notify"
  44.  
  45. ## Path:            System/Powermanagement/Powersave/Events
  46. ## Type:            string(notify,wm_shutdown,wm_logout,standby,suspend_to_disk,suspend_to_ram,screen_saver,ignore)
  47. #
  48. # The specified values(actions) will take effect, when the 
  49. # battery state changes from "low" to "critical".
  50. EVENT_BATTERY_CRITICAL="wm_shutdown"
  51.  
  52. # This event is never reached
  53. EVENT_BATTERY_NORMAL="ignore"
  54.  
  55. ## Path:            System/Powermanagement/Powersave/Events
  56. ## Type:            string(notify,wm_shutdown,wm_logout,standby,suspend_to_disk,suspend_to_ram,screen_saver,switch_vt,ignore)
  57. #
  58. # Button events. What functions of the proxy should be
  59. # triggered if a ACPI button is pressed?
  60. #
  61. # Hint: switch_vt could be useful for the LID_OPEN event (replace ignore)
  62. # some graphic cards might need switching to a virtual terminal
  63. # and back to let the X-server recover properly
  64. EVENT_BUTTON_POWER="wm_shutdown"
  65. EVENT_BUTTON_SLEEP="suspend_to_disk"
  66. EVENT_BUTTON_LID_OPEN="ignore"
  67. EVENT_BUTTON_LID_CLOSED="screen_saver"
  68.  
  69. ## Path:            System/Powermanagement/Powersave/Events
  70. ## Type:            string
  71. #
  72. # Gets processed if the powersave tool requests
  73. # a CPU frequency policy change. (e.g. powersave --performance)
  74. # These values are thought for later enhancements.
  75. # You may want to get your own function invoked to enable advanced
  76. # power saving functionalities.
  77. # However it would be easier to modify the binary that should
  78. # be invoked for the event in /etc/powersave.conf.
  79. EVENT_PROCESSOR_PERFORMANCE="ignore"
  80. EVENT_PROCESSOR_POWERSAVE="ignore"
  81. EVENT_PROCESSOR_DYNAMIC="ignore"
  82.  
  83. ## Path:            System/Powermanagement/Powersave/Events
  84. ## Type:        list(notify,wm_shutdown,wm_logout,standby,suspend_to_disk,suspend_to_ram,power_off,screen_saver)
  85. #
  86. # What should happen if a temperature limit is reached?
  87. EVENT_TEMPERATURE_CRITICAL="notify"
  88. EVENT_TEMPERATURE_HOT="notify"
  89. EVENT_TEMPERATURE_PASSIVE="ignore"
  90. EVENT_TEMPERATURE_ACTIVE="ignore"
  91. EVENT_TEMPERATURE_OK="ignore"
  92.  
  93. ## Path:            System/Powermanagement/Powersave/Events
  94. ## Type:            string
  95. #
  96. # This event gets thrown if a unknown event is encountered by the daemon.
  97. # Unknown events include e.g. ACPI hotkeys on some machines.
  98. # A description of this mechanism is available in
  99. # /usr/share/doc/packages/powersave/README.events.
  100. EVENT_OTHER="hotkey_handler"
  101.  
  102. ## Path:            System/Powermanagement/Powersave/Events
  103. ## Type:            string
  104. #
  105. # The kernel may inform that changes on CPU frequencies or throttling
  106. # states capabilites have been taken place.
  107. # In this case a cpu_notify event is generated by the powersave daemon and
  108. # the internal function reread_cpu_capabilities should be processed
  109. EVENT_PROCESSOR_NOTIFY="reread_cpu_capabilities"
  110.  
  111. ## Path:            System/Powermanagement/Powersave/Events
  112. ## Type:            string
  113. #
  114. # After the processor is idle (CPU_LOW) for a specific time
  115. # see a processor.idle event is thrown.
  116. # If the cpu usage goes beyond the CPU_HIGH value
  117. # a processor.busy event is thrown at once.
  118. # There will never be one event thrown twice in a row, they 
  119. # alternate! This is a perfect place to add additional
  120. # power saving functionalities.
  121. EVENT_PROCESSOR_BUSY="dethrottle"
  122. EVENT_PROCESSOR_IDLE="throttle"
  123.  
  124. ## Path:            System/Powermanagement/Powersave/Events
  125. ## Type:            string
  126. #
  127. # The specified functions that get processed
  128. # when an suspend/standby is requested should not be modified.
  129. # See System/Powermanagement/Powersave/Suspend or Standby
  130. # for possible modifications if you encounter problems
  131. # with these.
  132. # You should change those only if you know what you are doing,
  133. # if you remove e.g. the "screen_saver" event here, graphical
  134. # clients like kpowersave will no longer lock the screen on
  135. # suspend, no matter what. You have been warned :-)
  136. EVENT_GLOBAL_SUSPEND2DISK="prepare_suspend_to_disk screen_saver do_suspend_to_disk"
  137. EVENT_GLOBAL_SUSPEND2RAM="prepare_suspend_to_ram screen_saver do_suspend_to_ram"
  138. EVENT_GLOBAL_STANDBY="prepare_standby screen_saver do_standby"
  139.  
  140. EVENT_GLOBAL_RESUME_SUSPEND2DISK="restore_after_suspend_to_disk"
  141. EVENT_GLOBAL_RESUME_SUSPEND2RAM="restore_after_suspend_to_ram"
  142. EVENT_GLOBAL_RESUME_STANDBY="restore_after_standby"
  143.  
  144. ## Path:            System/Powermanagement/Powersave/Events
  145. ## Type:            string
  146. #
  147. # This event gets executed on suspend to disk if a suspend2
  148. # enabled kernel is found (/proc/suspend2 exists)
  149. EVENT_GLOBAL_SUSPEND2DISK_OTHER="suspend2"
  150.