Created a beta2 system with kde and gnome. Booted the new system and
changed some configuration -- (vmware xserver) and /etc/inittab. Rebooted
Brought up the new system and let it just "sit" for about ten minutes.
When I rebooted the system again, a message during shutdown indicated that
anacron shutdown "FAILED".
Considering anacron isn't a daemon and unless it is working on something that
is taking a long time normally wouldn't be running during shutdown, it doesnt
seem appropriate to show a [ FAILED ] notice for stopping anacron. Might as
well leave it alone and let it get hit with all the other process as a
TERM/KILL is sent.
Is it even a good idea to have anacron run at that point in the startup
anyway? A script placed in /etc/cron.* might require another service that
isn't running, such as a database server, a web server, a news server, etc.
Currently anacron is being started even before networking is up...
Fixed in 2.3-5.
It's treated like a daemon because we want it to be run at runlevel changes
(cron is not necessarily running in runlevel 1); someone messed up the ifs while
moving over to the new start() scheme.
*** Bug 14274 has been marked as a duplicate of this bug. ***