Hello, I am a bit surprise by the answers that I received. Again, cron and anacron used to run quite well for a long time. Both can co-live, one run periodically according to /etc/crontab and /etc/cron.daily /etc/cron.weekly, etc... and anacron could make the relay, in case that the machine was turned off. Why give up this logic? Now, we have /etc/crond.d with 0hourly raid-check /etc/cron.hourly with 0anacron /etc/cron.daily/ seems to be ignored Where is the logic? =========================================================================== Patrick DUPRÉ | | email: pdupre@xxxxxxx Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France =========================================================================== > Sent: Wednesday, September 21, 2016 at 6:27 PM > From: "Tom Horsley" <horsley1953@xxxxxxxxx> > To: users@xxxxxxxxxxxxxxxxxxxxxxx > Subject: Re: cron > > On Wed, 21 Sep 2016 10:26:14 -0400 > Matthew Miller wrote: > > > If you care about the *particular* time that a job runs, rather than > > just wanting to make sure it gets run once in a certain period, > > cron.daily and cron.weekly are not for you. Instead, drop a file in > > /etc/cron.d with the traditional > > Or utterly eradicate anacron and move the daily and weekly > jobs back to /etc/crontab (formatting the lines appropriately > for the system crontab file, mind you). > > That what I do, and I copy /dev/null over: > > /etc/cron.d/0hourly /etc/cron.hourly/0anacron /etc/anacrontab > > That way the scourge of anacron is gone forever :-). > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
