Description of problem:

Default apmd installation sets the following parameter in /etc/sysconfig/apmd:

LOWPOWER_SERVICES="atd crond"

Following a low-power situation (or even a full battery drain and subsequent
system failure), crond fails to restart.

The hardware involved is a Dell Latitude C610 laptop.

I considered including crond in RESTORESERVICES, but the comment block
specifically says "Any valid service ... can be listed, and will be restarted if
it was running at suspend time."  Since apmd has already shutdown crond, I
presume it will not be restarted using RESTORESERVICES.

Version-Release number of selected component (if applicable):

  Red Hat Linux 8.0 2.4.18-27.8.0
  apmd-3.0.2-12
  vixie-cron-3.0.1-69

How reproducible:

As far as I can tell, every time.  I haven't done extensive experiments to see
if it is each time the battery gets to low power, or even what low power
percentage that is.  I also haven't checked to see if this is affected by doing
a suspend, although it definitely has happened without a suspend.

Steps to Reproduce:
1.  Unplug AC power from system
2.  Let system run until it reaches low-power threshold
3.  Plug back in and let battery charge, check to see if crond is running
    
Actual results:

crond is not restarted by apmd when coming back from a low-power battery situation

Expected results:

crond is restarted by apmd

Additional info:

I can presumably run some more tests, but they take some time and planning - it
takes a couple of hours for my battery to drain enough to go to a low-power
situation.  Let me know if this would be helpful.