Red Hat Bugzilla – Bug 487686
anacron has lost its marbles, is round the bend, is off its chum, has gone mental...
Last modified: 2009-03-02 09:12:33 EST
Description of problem:
I just got mail that anacron just ran cron.weekly. The normal cron.weekly
job ran just fine early Sunday morning like always. The next cron.weekly
job isn't scheduled to run until next Sunday. What in the blue blazes
is anacron doing running it now? Any missed cron activity was entirely
in anacron's imagination.
Version-Release number of selected component (if applicable):
Apparently utterly random.
Steps to Reproduce:
1. No idea.
Anacron running stuff for no reason at all.
Anacron acting sane.
I actually don't want anacron at all. This machine is up 99% of the time
and if it happens to be down when cron has a job scheduled, too bad, it
will get it the next time. I just removed anacron in an attempt to stop
the insanity, but I see another bugzilla that claims everything stops
working without anacron. I hope that is only in rawhide.
I have often suspected similar nonsense with cron.daily, but this weekly
run in the middle of the week is far too obvious to overlook.
I looked in the yum log and see that anacron-2.3-66.fc10.i386
just arrived in updates yesterday. Did it completely change the
way it does everything or something and therefore convinced
itself that cron.weekly hadn't run this week?
For F-10 it was only updates, so that was only bug fixing #477709. Users confirm the fix.
As reported on F-10 closing as duplicate. The update spent a long time in testing, so I suppose it's tested well.
*** This bug has been marked as a duplicate of bug 477709 ***