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
/
common
< prev
next >
Wrap
Text File
|
2007-02-24
|
6KB
|
158 lines
## Path: System/Powermanagement/Powersave
## Description: The Powersave package joins the capabilities of the ACPI daemon, \
## APM daemon and CPUfreq daemon. It provides a unified configuration \
## interface for your whole powermanagement. Be careful that you do not \
## run the mentioned daemons together with the powersave daemon.
## Path: System/Powermanagement/Powersave
## Type: integer(0:1000)
#
# Version of the configuration. Needed for future updates,
# DO NOT CHANGE MANUALLY!
CONFIG_VERSION="10"
## Path: System/Powermanagement/Powersave/General
## Description: General Power Management settings
## Path: System/Powermanagement/Powersave/General
## Type: integer(0:31)
## Default: "3"
## ServiceRestart: powersave
#
# Set the debug level, allowed values: 0-31
# 1 Error
# 2 Warning
# 4 Diag
# 8 Info
# 16 Debug
# e.g. Error + Warning: 1 + 2 -> 3
# powersaved needs restart to activate level, sending SIGHUP is not
# enough. Proxy scripts react immediately.
#
DEBUG=""
####### Y A S T 2 C O N F I G U R A T I O N S #######
## Path: System/Powermanagement/Powersave/General
## Type: string
## Default: "performance"
#
# Defines which scheme(system settings) should be used when
# the machine works on AC power.
# Have a look into the YaST Power Management Module to create
# new schemes. You can also set this variable there.
#
AC_SCHEME="performance"
## Path: System/Powermanagement/Powersave/General
## Type: string(powersave,performance,acoustic)
## Default: "powersave"
#
# Defines which scheme(system settings)
# should be used when the system works on battery power.
# Have a look into the YaST Power Management Module to create
# new schemes. You can also set this variable there.
#
BATTERY_SCHEME="powersave"
## Path: System/Powermanagement/Powersave/General
## Type: string(notify_popup_fallback notify_popup_window notify_console notify_acoustic none)
## Default: "notify_popup_fallback notify_acoustic"
#
# How should the user be notified by the notify method
# which could be assigend to several variables in System/Powermanagement/Powersave/Events.
# More than one value is assignable, "none" disables notification.
#
NOTIFY_METHOD=""
## Path: System/Powermanagement/Powersave/General
## Type: string(ac,battery,button,fan,processor,thermal,asus_acpi,toshiba_acpi)
## Default: "ac battery button fan processor thermal"
## ServiceRestart: powersaved
#
# The acpid startscript will load all necessary modules for acpi. If some of
# these modules cause trouble, you may remove it from this variable. You may
# add the modules asus_acpi or toshiba_acpi if your computer is an Asus or a
# Toshiba. Seperate several modules by space.
# If this variable is empty, the default is used. If you want to disable
# module loading, enter "NONE".
#
ACPI_MODULES=""
## Path: System/Powermanagement/Powersave/General
## Type: string(ac,battery,button,fan,processor,thermal)
## Default: "ac battery button fan processor thermal"
## ServiceRestart:
#
# The powersaved startscript will unload all loaded ACPI modules, when powersaved is
# stopped. If some modules cause trouble when unloading, you may add them to
# this variable. All modules in this list won't be unloaded. Note that some
# other of these modules might be unloadable as well, but that should not harm..
#
ACPI_MODULES_NOT_TO_UNLOAD=""
## Path: System/Powermanagement/Powersave/General
## Type: list(GRUB,LILO,OTHER)
## Default: "GRUB"
#
# Set this variable to the boot loader you are using.
# Only GRUB has an effect since LILO support is not implemented yet.
# If you don't want to automatically boot into the kernel you suspended
# with (or you don't use grub as boot loader), set this to anything else
# than GRUB.
BOOT_LOADER=""
## Path: System/Powermanagement/Powersave/General
## Type: integer(1:10000)
## Default: "333"
#
# The powersave daemon watches the usage of your CPU
# and other hardware concerning power consumption
# Please set the time in milliseconds for what the
# daemon should sleep before checking your system again
# Good values are about 200-1000(milliseconds)
#
POLLING_INTERVAL=""
## Path: System/Powermanagement/Powersave/General
## Type: yesno
## Default: "yes"
#
# Should the screensaver() function also switch off the
# display e.g. on lid close event? On some machines where
# the display is not shut off via hardware switch, this is
# required, on all others it should not harm.
# This setting has no effect when using a graphical client like kpowersave.
SCREENSAVER_DPMS_OFF=""
## Path: System/Powermanagement/Powersave/General
## Type: yesno
## Default: "no"
#
# If this is set to "yes", the screensaver will be instructed to only blank
# the screen and not display fancy graphics. This can cause confusion after
# resume since the screen will just stay black until you press a key. On the
# other hand, the fancy graphics may run down your battery faster.
# Choose your poison here.
# This setting has no effect when using a graphical client like kpowersave.
SCREENSAVER_BLANKONLY=""
## Path: System/Powermanagement/Powersave/General
## Type: integer(1:100)
## Default: "0"
#
# Set a value to delay the execution of the action
# bound to the power button.
# This could be useful if the action should not be
# triggered before the machine is possibly switched
# of by holding the power button for some seconds.
#
POWERBTN_DELAY=""
## Path: System/Powermanagement/Powersave/Scheme/General
## Type: yesno
## Default: "no"
#
# Enable runtime device power management. This feature is still some kind of
# experimental, so please be careful. Specific devices will be powered
# down if this feature is enabled. See DPM_CLASSES variable in scheme config
# files for further options.
ENABLE_DPM=""