--- apmd.ORIG        2004-11-06 15:00:47.759645376 -0800
+++ apmd        2004-11-06 15:00:31.655093640 -0800
@@ -1,3 +1,6 @@
+# 2004.10.19    wdw added cpufreq governors and comments
+#               and enabled POWER_SERVICES
+
 APMSCRIPTS=/etc/sysconfig/apm-scripts
 
 # make an entry in the logfiles whenever the percentage of
@@ -84,7 +87,7 @@
 # "/sbin/service ... stop" for each of the services).
 # If you want to stop/restart any services that are not started by the init system,
 # use an apmcontinue script.
-#POWER_SERVICES="atd crond"
+POWER_SERVICES="atd crond autofs cups pcmcia syslog"
 
 # If you wish to stop any services when running short of battery power (and restart them when
 # going to line power), list them in LOWPOWER_SERVICES.
@@ -104,5 +107,20 @@
 
 # If your machine supports using cpufreq to change its speed, you can enable
 # this to support changing the cpu frequence to performance or powersave
-# based on whether or not you are currently on AC power or battery power
-#CPUFREQ="no"
+# based on whether or not you are currently on AC power or battery power.
+#
+# Selecting yes allows the apmscript to use the governors specified below.
+# Leaving commented out allows a userspace governor (cpuspeed, cpuspeed2...)
+# to control CPU clock frequency based on demand and other parameters.
+# CPUFREQ="yes"
+
+# If you set CPUFREQ to yes, you can specify the governors to be used when
+# AC is on-line or off-line.  Requires newer cpufreq interface in
+# /sys/devices/system/cpu/cpu0/cpufreq.
+#
+# current choices are: performance and powersave.  Do not specify the
+# userspace governor.  See Documentation/cpu-freq for details.
+# These are the same as the apmscript defaults - included here for completeness.
+#AC_ONLINE_GOVERNOR="performance"
+#AC_OFFLINE_GOVERNOR="powersave"
+