# Startup options
#################

# To learn more about this startup options see man apmd and the startup
# script /sbin/init.d/apmd.

# If you like to be warned when battery capacity goes below a certain level,
# you can set this level here in % maximum battery capacity. Set it to "0"
# to switch this and the following 3 options off.
# Default: "10" 
APMD_WARN_LEVEL="10"

# Do you like this warning send to all terminals then set this to "yes".
# Otherwise you find the warnings in your syslog file.
# Default: "no"
APMD_WARN_ALL="no"

# This warning can be repeated everytime the capacity has decreased by
# "WARN_STEP" % of the maximum battery capacity. "0" means off.
# Default: "0"
APMD_WARN_STEP="0"

# By default apmd checks the battery status everytime it gets an event from
# the BIOS. If you like it to be checked more often, set it to a value
# greater than 0 seconds.
# NOTE: this wakes up your disk at every check :(
# Default: "0"
APMD_CHECK_TIME="0"

# Make the apmd and the apmd_proxy-script more verbose. Anything but "no" 
# does it. If set to "logfile" the apmd_proxy-script logs all commands to 
# /tmp/apmd_proxy.log.  
# Default: "no"
APMD_DEBUG="no"

# Runtime options --- when power changes
########################################

# For saving power you should let your harddisk spin down after an idle
# time. That is not needed when on wall power. Set ADJUST_DISK_PERF to
# "yes" if apmd should check this. Note that this does not help much, if
# any process (like an text editor) writes frequently to your disk.
# Default: "no"
APMD_ADJUST_DISK_PERF="no"

# Set the timeout for your disk to spin down, when on battery and when on
# AC power. You must set ADJUST_DISK_PERF to "yes" to let this work. The
# values are not just seconds or minutes. It's a bit tricky. 
# From man hdparm (option -S):
#                                               .... The encoding
#             of the timeout value is somewhat peculiar.  A value
#             of  zero means "off".  Values from 1 to 240 specify
#             multiples of 5 seconds, for timeouts from 5 seconds
#             to 20 minutes.  Values from 241 to 251 specify from
#             1 to 11 units of 30 minutes, for timeouts  from  30
#             minutes  to  5.5 hours.  A value of 252 signifies a
#             timeout of 21 minutes, 253  sets  a  vendor-defined
#             timeout,  and 255 is interpreted as 21 minutes plus
#             15 seconds.
# Default: "12" (1 minute)
APMD_BATTERY_DISK_TIMEOUT="12"
# Default: "0" (off, no spindown)
APMD_AC_DISK_TIMEOUT="0"

# Normaly the update-daemon every 30 secs flushes the disk buffers to
# the disk. Metadata as fileownership and timestamps are written even
# every 5s. So your disk won't sleep for longer than 30s, if any file
# has been changed. You can modify that behavior to wait longer before
# a disk syncronisation. But beware, that all data that was not synced
# will be lost, if your machine crashes in between. If your system is
# running stable, you can save much more power, by doing this.
# There are 3x2 variables to modify this: 
# - the time to max. wait before syncing data
# - the time to max. wait before syncing metadata
# - the fill level of the disk buffers that triggers a sync
# > each of these for battery mode and ac mode.
# Default: "30" seconds
APMD_BATTERY_DATA_TIMEOUT="30"
# Default: "5" seconds
APMD_BATTERY_METADATA_TIMEOUT="5"
# Default: "40" %
APMD_BATTERY_FILL_LEVEL="40"
# Default: "30" seconds
APMD_AC_DATA_TIMEOUT="30"
# Default: "5" seconds
APMD_AC_METADATA_TIMEOUT="5"
# Default: "40" %
APMD_AC_FILL_LEVEL="40"


# When the battery capacity becomes very low some Laptop BIOSs send an 
# "battery low" message. You can then let your machine shut down a few
# minutes later. Set the number of minutes here. Minumum is 1 minute, 
# a value of "0" switches this behavior of.
# Default: "0"
APMD_BATTERY_LOW_SHUTDOWN="0" # minutes


# Runtime options --- suspend and resume stuff
##############################################

# If you have problems with wrong timesettings after a standby 
# or suspend, set SET_CLOCK_ON_RESUME to "yes". The kerneltime will
# be set according to the value stored in the GMT-variable.
# Default: "no"
APMD_SET_CLOCK_ON_RESUME="yes" 

# Set SUSPEND_ON_AC to "no" if you wish to avoid suspend and standby
# events when your machine is connected to AC power. By default
# suspends can occur on either battery or AC power. An suspend 
# requested by the user is executed anyway.
# NOTE: The SuSE 6.3 kernel (2.2.13) does NOT yet support this.
# NOTE: This feature is dedicated for a future release
# Default: "yes"
APMD_SUSPEND_ON_AC="yes"

# If PCMCIA is compiled with APM-Support, cards are normally suspended 
# before your system suspends. If you don't have APM-Support in PCMCIA,
# you can let apmd do this job. The SuSE PCMCIA package does note have
# APM support, because it is not reliable. Set it here, if you need it.
# Default: "no"
APMD_PCMCIA_SUSPEND_ON_SUSPEND="no"

# PCMCIA cards can be more or less amenable to an APM suspend event.
# If you have a card that cannot be suspended properly (such as a SCSI
# card), then it should be "ejected" before entering suspend mode. The
# cards are not physically ejected; rather, the power is turned off to
# them via the "cardctl eject" command, and is reactivated upon resume.
# Default: "no"
APMD_PCMCIA_EJECT_ON_SUSPEND="no"

# If your graphic device is not able to return properly from suspend
# you can switch to textconsole before suspend and return to your
# X-console after resume.
# Default: "no"
APMD_LEAVE_X_BEFORE_SUSPEND="yes"
# Sometime you even need it when standby.
# Default: "no"
APMD_LEAVE_X_BEFORE_STANDBY="no"

# Sometimes the soundmodules do not survive a suspend/resume cycle.
# In this case everything seems to be OK, but you can't hear anything.
# To avoid this the soundmodules can be unloaded before suspend. A reload
# of this modules will only be done if you use ALSA or OSS. If you use 
# modules from the kernel they will be reloaded automatically. If you like
# that, set APMD_STOP_SOUND_BEFORE_SUSPEND to "alsa", "oss" or "kernel",
# depending on what type of sound system you are using.
# To unload all soundmodules succesfully, all soundapplications that are
# currently using some of them must be killed. So don't wonder if you miss
# an already started soundapplication after suspend/resume.
# Default: "no" possible values: "alsa", "oss", "kernel"
APMD_STOP_SOUND_BEFORE_SUSPEND="no"