=========================================================================== 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: Friday, September 23, 2016 at 10:06 AM > From: "Jon LaBadie" <jonfu@xxxxxxxxxx> > To: users@xxxxxxxxxxxxxxxxxxxxxxx > Subject: Re: cron > > On Fri, Sep 23, 2016 at 09:52:30AM +0200, Patrick Dupre wrote: > > > > > From: "Jon LaBadie" <jonfu@xxxxxxxxxx> > > > To: users@xxxxxxxxxxxxxxxxxxxxxxx > > > Subject: Re: cron > > > > > > On Thu, Sep 22, 2016 at 06:56:07PM -0400, Tom Horsley wrote: > > > > On Thu, 22 Sep 2016 23:56:04 +0200 > > > > Patrick Dupre wrote: > > > > > > > > > anacron weakly is supposed to run on saturday, it run on Monday now ! > > > > > Same thing for cron ! > > > > > > > > There is no "supposed to" with anacron. It decides when to run > > > > stuff for it's own wacky reasons. Did you install f24 on > > > > a Monday? It may have decided if Monday was the first day it > > > > thought it ran, that it would always run weekly jobs on Monday. > > > > > > > > > > Good supposition. > > > I upgraded to F24 on a Friday and my cron.weekly runs on Fridays. > > > > > I upgraded on a Sunday > > Perhaps it took until after 10PM. In that case anacron would not > run weekly until after 3AM Monday. From /etc/anacrontab: This can be the right explanation > > # the jobs will be started during the following hours only > # START_HOURS_RANGE=3-22 > > Regardless, as has been said before, if you want a job run at > specific times, anacron is not the correct tool. Use cron. > Yes and no, Monday is not a good day. I would like to move to Saturday Why not a START_DAYS_RANGE ? for the weekly stuff ? Thank _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
