Description of problem: Freshly updated anacron complains on every startup that it failed to connect to hald and that most likely means that the later is not running (while actually it does run). I do not have an exact wording of an error message as this happens _only_ in a startup sequence and is quickly erased by a login screen even when booting to level 3. When trying 'service anacron start' after a login then it just shows "[OK}" without any complaints. In log file one can find "INFO (running with inotify support)" so maybe an error shown on a screen is bogus? Version-Release number of selected component (if applicable): anacron-2.3-66.fc11 How reproducible: on every startup and only then
Thank you, fixed in rawhide.
Yeah, looking closer you are right that this is not anacron problem. This is another instance of bug 479180; only this time with haldaemon service which is running too late. After 'chkconfig haldaemon off; chkconfig haldaemon on' "startup links" switch from S98haldaemon to S26haldaemon and anacron starts with S95. I just looked at "# chkconfig: 345 26 74" line in /etc/init.d/haldaemon and got mislead by it. How this is "fixed in rawhide"? Just changing startup scripts does not make it so. Upgrades will bump into the same issue.
The error message was sent to /dev/null but anyway there will be changes which probably remove anacron "init" script at all.
*** Bug 482979 has been marked as a duplicate of this bug. ***