Red Hat Bugzilla – Bug 508457
make anacron stop!
Last modified: 2009-08-14 08:50:22 EDT
Description of problem:
In fedora 10 and before, I could eradicate the random pestilence of anacron
by disabling the anacron service. In fedora 11 I found there was no service
and the way to disable it was to "yum erase anacron" (and put back my fedora
10 style /etc/crontab), with the latest cronie update, there is now a dependency
on anacron, so it wants to drag this monstrosity back onto my system.
For Gods sake, please provide (and document in the anacron man page)
the official, sure to remain effective despite constant changes in packaging
way to utterly disable anacron. (Maybe an /etc/sysconfig/anacron file with
Version-Release number of selected component (if applicable):
Highly persistent little bugger.
Steps to Reproduce:
Anacron keeps returning in bad sequels.
Anacron stays dead once I put a stake through its heart.
I did my best to put anacron to sleep. His so called daemon was removed.
The main problem are conflicting thoughts about cronjobs on desktop vs. server. Details could be find in manuals: crontabs, anacrontab(5). My plans are merge anacron and cronie into one which has to wipe out pestilence for good.
I don't know - putting them together sounds like there would be no way
to ever make it stop trying to recover - it is the botched attempts to
rerun things which I want to remove. If it skipped a run, then it
skipped a run - don't help me :-).
At the moment, I've erased the contents of:
/etc/cron.d/0hourly /etc/cron.hourly/0anacron /etc/anacrontab
and put back the old f10 /etc/crontab and that is doing exactly
what I want (which is to get no "help" of any kind from anacron :-).
If they get merged into one, please have something like a
/etc/sysconfig/cron flag I can set to say "Never under any
circumstances attempt to rerun a job you imagine you missed."
(In reply to comment #2)
> I don't know - putting them together sounds like there would be no way
> to ever make it stop trying to recover - it is the botched attempts to
> rerun things which I want to remove. If it skipped a run, then it
> skipped a run - don't help me :-).
If you set START_HOURS_RANGE to your preferred time range when jobs should started, then they will start _only_ in this range. In case there will be skipped then they will be skipped and won't be executed that day. However for you there will be some option f.e. NO_ANACRON.
for switching off.