eradicating f11 anacron
As near as I can tell, the new and improved anacron in fedora 11 has seized control of all the cron.daily, cron.weekly, etc jobs. As a consequence, if you yum erase anacron None of the normal background cron processing will happen (how convenient :-). Here's my current formulae for eradicating anacron: service crond stop yum --disablerepo=* erase anacron mv /etc/crontab /etc/crontab.orig cp /etc/crontab service crond start Anyone see anything wrong with that? I guess I'll find out tomorrow if my nightly backup runs. If I had selinux turned on, it would no doubt throw some kind of hissy-fit over the copied in crontab file, but I don't have selinux turned on :-). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eradicating f11 anacron
On Thu, 18 Jun 2009 20:50:22 -0400 Tom Horsley wrote: > I guess I'll find out > tomorrow if my nightly backup runs. Hey! It worked. I have successfully eradicated the scourge of anacron (sounds like a movie on the sci-fi channel :-). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eradicating f11 anacron
Tom Horsley wrote: > As near as I can tell, the new and improved anacron > in fedora 11 has seized control of all the cron.daily, > cron.weekly, etc jobs. What's wrong with anacron? I have my backup script listed in anacrontab and never have to even think about it: anacron runs before I retire, or if I retire earlier, then the first thing in the morning. And you don't have to bother with configuring BOTH crontab AND anacrontab, like you used to have to. What could be easier and more convenient? I like this new setup. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eradicating f11 anacron
On Fri, 19 Jun 2009 09:48:16 -0600 Petrus de Calguarium wrote: > What's wrong with anacron? It is pointless stupid and annoying :-). It constantly picks highly inconvenient times to rerun cron jobs it thinks it didn't run, but it is almost always wrong about that because of the way things like the /etc/cron.daily script are setup. There are a dozen scripts in there. It runs the daily job, completing 11 of 'em, then I need to reboot or there is a power flicker or something. At some random time, it says to itself "OMG! cron.daily didn't finish, I'll just rerun all 12 of the scripts again". I find it much more sensible and convenient to have the dadgum cron jobs run when they are supposed to run, and if I take the machine down, it is my problem if they didn't run and it is up to me to fix (or ignore). If I erase anacron, I don't have to configure two crontabs either, just the one, but it is much more predictable :-). It used to be simple - I'd just disable the anacron service, and no more annoying anacron. Now I need to reconfigure the crontab I used to have. I hate this new setup :-). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eradicating f11 anacron
Tom Horsley wrote: > If I erase anacron, I don't have to configure two > crontabs either, just the one, but it is much more > predictable :-). I was getting frustrated with CRON because it WASN'T predictable. With this damned delay there is now, you never know when it's going to run. Anacron has a delay now, too, but it is easy to circumvent. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eradicating f11 anacron
On Fri, 19 Jun 2009 10:49:59 -0600 Petrus de Calguarium wrote: > I was getting frustrated with CRON because it WASN'T > predictable. With this damned delay there is now, you never know > when it's going to run. Anacron has a delay now, too, but it is > easy to circumvent. It is easy in cron too, just diddle the /etc/sysconfig/crontab file where one of the bits of info it uses for delays is stashed (I tracked that down by reading the /etc/init.d/crond script :-). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eradicating f11 anacron
Tom Horsley wrote: > It is easy in cron too Since I regularly turn off my computer (whenever I go out, night-time, etc), I feel that the present setup with anacron is best for me. A strange cronie/crontab update just now appeared on my laptop (PAE/i586), but not on my desktop (x86_64). It is a file called /etc/sysconfig/crontab.rpmsave. It has the delay variable in it. I suppose I should rename it to /etc/sysconfig/crontab? It doesn't appear to replace /etc/sysconfig/crond nor /etc/crontab. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eradicating f11 anacron
Petrus de Calguarium wrote: > Tom Horsley wrote: > >> It is easy in cron too > > Since I regularly turn off my computer (whenever I go out, > night-time, etc), I feel that the present setup with anacron is > best for me. > > A strange cronie/crontab update just now appeared on my laptop > (PAE/i586), but not on my desktop (x86_64). It is a file called > /etc/sysconfig/crontab.rpmsave. It has the delay variable in it. > I suppose I should rename it to /etc/sysconfig/crontab? It > doesn't appear to replace /etc/sysconfig/crond nor /etc/crontab. > It is your /etc/sysconfig/crontab from before the update. The new RPM installed a new crontab, and saved the old one as crontab.rpmsave. This is common when the new version changed the configuration file format, and you have made changes to the old version's configuration file. This lets you transfer the information to the new format, if you need it. (.rpmsave = backup of old configuration, new file used. .rpmnew = new configuration file, old file still being used.) Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eradicating f11 anacron
Mikkel L. Ellertson wrote: > It is your /etc/sysconfig/crontab from before the update. Thanks. Yes, I already knew that. What was strange, however, was that there was no original /etc/sysconfig/crontab, only this new one. My x86_64 system doesn't have that file either, only /etc/sysconfig/crond and /etc/crontab, but no /etc/sysconfig/crontab. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: eradicating f11 anacron
Petrus de Calguarium wrote: > Mikkel L. Ellertson wrote: > >> It is your /etc/sysconfig/crontab from before the update. > > Thanks. Yes, I already knew that. > > What was strange, however, was that there was no original > /etc/sysconfig/crontab, only this new one. My x86_64 system > doesn't have that file either, only /etc/sysconfig/crond and > /etc/crontab, but no /etc/sysconfig/crontab. > Maybe it is left over from an upgrade? I have one in F10, but I used pre-upgrade to migrate it from F8. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
