Hello,
Finally, I still do not know how to manage the schedule for cron.weekly and cron.daily, since /etc/anacrontab or /etc/crontab are just ignored in fc24.
Thank.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com 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 ===========================================================================
On 09/20/2016 03:52 PM, Patrick Dupre wrote:
Finally, I still do not know how to manage the schedule for cron.weekly and cron.daily, since /etc/anacrontab or /etc/crontab are just ignored in fc24.
Why do you think that? My cron.weekly and cron.daily get run and they are referenced from /etc/anacrontab.
On 09/20/2016 04:17 PM, Samuel Sieb wrote:
On 09/20/2016 03:52 PM, Patrick Dupre wrote:
Finally, I still do not know how to manage the schedule for cron.weekly and cron.daily, since /etc/anacrontab or /etc/crontab are just ignored in fc24.
Why do you think that? My cron.weekly and cron.daily get run and they are referenced from /etc/anacrontab.
Patrick, make sure you have the crond.service enabled:
[root@prophead ~]# systemctl list-unit-files *cron* UNIT FILE STATE crond.service enabled
If it's not enabled, then
sudo systemctl enable crond.service sudo systemctl start crond.service
The crond.service is responsible for both normal crond AND anacrond operations (they're not separated anymore) and it works perfectly well. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - I haven't lost my mind. It's backed up on tape somewhere, but - - probably not recoverable. - ----------------------------------------------------------------------
Hello,
crond is running
UNIT FILE STATE crond.service enabled
1 unit files listed.
But this is what I have in my /etc/crontab: 22 23 * * * root run-parts /etc/cron.daily 06 13 * * 6 root run-parts /etc/cron.weekly
and in my /etc/anacrontab 1 5 cron.daily nice run-parts /etc/cron.daily 7 25 cron.weekly nice run-parts /etc/cron.weekly
but
anacron is executed on the Monday ! N 44 Monday root (793) Backup N 45 Monday root (818) Backup N 46 Monday Anacron (2K) Anacron job 'cron.weekly' on teucidide
While in fc22, with the same configuration, crond and anacrond were executed on time (Saturday)
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com 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 1:17 AM From: "Samuel Sieb" samuel@sieb.net To: "Community support for Fedora users" users@lists.fedoraproject.org Subject: Re: cron
On 09/20/2016 03:52 PM, Patrick Dupre wrote:
Finally, I still do not know how to manage the schedule for cron.weekly and cron.daily, since /etc/anacrontab or /etc/crontab are just ignored in fc24.
Why do you think that? My cron.weekly and cron.daily get run and they are referenced from /etc/anacrontab. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On Wed, Sep 21, 2016 at 10:02:19AM +0200, Patrick Dupre wrote:
and in my /etc/anacrontab 1 5 cron.daily nice run-parts /etc/cron.daily 7 25 cron.weekly nice run-parts /etc/cron.weekly
but
anacron is executed on the Monday ! N 44 Monday root (793) Backup N 45 Monday root (818) Backup N 46 Monday Anacron (2K) Anacron job 'cron.weekly' on teucidide
While in fc22, with the same configuration, crond and anacrond were executed on time (Saturday)
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
0 4 * * sat root yourcommand.sh
syntax (in that example, to run yourcommand.sh as root at 4am on Saturdays).
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 :-).
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@gmx.com 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@gmail.com To: users@lists.fedoraproject.org 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@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On Wed, 21 Sep 2016 19:26:18 +0200 Patrick Dupre wrote:
Why give up this logic?
Because my machine is never turned off, and anacron has the uncanny ability to make things run at the most inconvenient possible times to interfere with things I'm trying to do.
Cron runs thing when I want them to run.
Then,
What about a laptop?
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com 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 7:45 PM From: "Tom Horsley" horsley1953@gmail.com To: users@lists.fedoraproject.org Subject: Re: cron
On Wed, 21 Sep 2016 19:26:18 +0200 Patrick Dupre wrote:
Why give up this logic?
Because my machine is never turned off, and anacron has the uncanny ability to make things run at the most inconvenient possible times to interfere with things I'm trying to do.
Cron runs thing when I want them to run. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On 09/21/2016 10:45 AM, Tom Horsley wrote:
On Wed, 21 Sep 2016 19:26:18 +0200 Patrick Dupre wrote:
Why give up this logic?
Because my machine is never turned off, and anacron has the uncanny ability to make things run at the most inconvenient possible times to interfere with things I'm trying to do.
You do know you can modify the "START_HOURS_RANGE=" parameter in /etc/anacrontab to tell anacron when it is permitted to run things, right? By default it's set to "3-22" permitting things to be run between 3 a.m. and 10 p.m. If that's inconvenient, then perhaps changing it to
START_HOURS_RANGE=2-7
(permit runs between 2 and 7 a.m.) might work.
Cron runs thing when I want them to run.
Well, yes, of course. Remember that anacron is really intended to do "housekeeping" stuff like rebuilding the man pages, updating the locate databases and such when the machine isn't busy and to ensure they get done even if the power has been off for a while.
It's up to you to tell it when the machine "isn't going to be busy". I agree that the defaults of 0300 through 2200 is likely to include the times the machine is in use, but it's easy enough to alter.
If you want to disable anacron but leave it installed, just
echo "0anacron" >>/etc/cron.hourly/jobs.deny
That prevents anacron from running (anacron is launched by cron every hour and that tells cron NOT to run it) ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - A friend said he climbed to the top of Mount Rainier. My view is - - that if there's no elevator, it must not be that interesting. - ----------------------------------------------------------------------
On Wed, 21 Sep 2016 11:30:49 -0700 Rick Stevens wrote:
You do know you can modify the "START_HOURS_RANGE=" parameter in /etc/anacrontab to tell anacron when it is permitted to run things, right?
Yep. I also know I can completely eradicate anacron :-).
If you want to disable anacron but leave it installed, just
echo "0anacron" >>/etc/cron.hourly/jobs.deny
But unless you fix your crontab as well, that also completely disables everything anacron has taken over, like cron.daily and cron.weekly.
On Wed, Sep 21, 2016 at 07:26:18PM +0200, Patrick Dupre wrote:
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?
I'm not sure where your and my systems differ. But on mine, cron.daily is certainly NOT ignored. I get daily logwatch reports from there and my locate database is updated from there.
In fact, since I learned about the systemD mechanism for daily updates of the locate database, I activated it to see the effect and I'm getting twice daily updates.
The crond manpage says it reads /etc/anacrontab. It is from there that daily/weekly/monthly get executed.
Jon
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com 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: Thursday, September 22, 2016 at 7:14 AM From: "Jon LaBadie" jonfu@jgcomp.com To: users@lists.fedoraproject.org Subject: Re: cron
On Wed, Sep 21, 2016 at 07:26:18PM +0200, Patrick Dupre wrote:
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?
I'm not sure where your and my systems differ. But on mine, cron.daily is certainly NOT ignored. I get daily logwatch reports from there and my locate database is updated from there.
In fact, since I learned about the systemD mechanism for daily updates of the locate database, I activated it to see the effect and I'm getting twice daily updates.
The crond manpage says it reads /etc/anacrontab. It is from there that daily/weekly/monthly get executed.
This was correct with fc22, but sine I updated in fc24. The behavior is not correct. cf. anacron weakly is supposed to run on saturday, it run on Monday now ! Same thing for cron ! It is why I am complaining. And I cannot get any explanation why the behavior of my machine has changed after the update while the configuration files /etc/anacrontab and /etc/crontab did not change
Jon
Jon H. LaBadie jonfu@jgcomp.com _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
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.
This is why I always hit it with my big hammer and move everything back to 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.
Jon
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com 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 2:13 AM From: "Jon LaBadie" jonfu@jgcomp.com To: users@lists.fedoraproject.org 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
On Fri, Sep 23, 2016 at 09:52:30AM +0200, Patrick Dupre wrote:
From: "Jon LaBadie" jonfu@jgcomp.com To: users@lists.fedoraproject.org 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:
# 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.
jl
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com 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@jgcomp.com To: users@lists.fedoraproject.org Subject: Re: cron
On Fri, Sep 23, 2016 at 09:52:30AM +0200, Patrick Dupre wrote:
From: "Jon LaBadie" jonfu@jgcomp.com To: users@lists.fedoraproject.org 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
On Fri, Sep 23, 2016 at 01:32:00PM +0200, Patrick Dupre wrote:
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 ?
why not USE CRON ?
jl
Hello,
In fc22, anacron and crond where both running simultaneously fine. No any more in fc24 : it seems that now crond only run hourly and ignore the weekly (and daily) tasks. That I wish to restablish.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com 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 8:10 PM From: "Jon LaBadie" jonfu@jgcomp.com To: users@lists.fedoraproject.org Subject: Re: cron
On Fri, Sep 23, 2016 at 01:32:00PM +0200, Patrick Dupre wrote:
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 ?
why not USE CRON ?
jl
Jon H. LaBadie jonfu@jgcomp.com _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On Fri, Sep 23, 2016 at 09:23:43PM +0200, Patrick Dupre wrote:
In fc22, anacron and crond where both running simultaneously fine. No any more in fc24 : it seems that now crond only run hourly and ignore the weekly (and daily) tasks. That I wish to restablish.
Do you have cronie-anacron installed?
On Fri, Sep 23, 2016 at 09:23:43PM +0200, Patrick Dupre wrote:
From: "Jon LaBadie" jonfu@jgcomp.com On Fri, Sep 23, 2016 at 01:32:00PM +0200, Patrick Dupre wrote:
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 ?
why not USE CRON ?
Hello,
In fc22, anacron and crond where both running simultaneously fine. No any more in fc24 : it seems that now crond only run hourly and ignore the weekly (and daily) tasks. That I wish to restablish.
And I've noted several times in this thread that is not the case here. On my F24 system I have several crontabs, each with multiple entries. I also have things run by anacron from cron.daily, and cron.weekly. Further I have some things, like the locate database update being run by systemD timers.
Please consider that your F24 setup is incomplete or has some errors and your experience is not the norm.
Jon
On Fri, 23 Sep 2016 17:49:34 -0400 Jon LaBadie wrote:
Please consider that your F24 setup is incomplete or has some errors and your experience is not the norm.
It works fine for me with everything moved into cron.
Here's my /etc/crontab:
SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root HOME=/
# run-parts 01 * * * * root run-parts /etc/cron.hourly/ 02 4 * * * root run-parts /etc/cron.daily/ 22 4 * * 0 root run-parts /etc/cron.weekly/ 42 4 1 * * root run-parts /etc/cron.monthly/
My /etc/anacrontab is empty (because I copied /dev/null to it), and my /etc/cron.hourly/0anacron file is also empty for the same reason.
This removes everything from anacron and runs things at actually predictable times on cron.
You might ask, "Why not just remove anacron?". This totally absurd nonsense happens when you try that:
[root@zooty ~]# dnf erase cronie-anacron Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Removing: ceph x86_64 1:10.2.2-2.fc24 @updates 0 ceph-base x86_64 1:10.2.2-2.fc24 @updates 24 M ceph-mds x86_64 1:10.2.2-2.fc24 @updates 9.3 M ceph-mon x86_64 1:10.2.2-2.fc24 @updates 9.2 M ceph-osd x86_64 1:10.2.2-2.fc24 @updates 31 M ceph-selinux x86_64 1:10.2.2-2.fc24 @updates 102 k cronie x86_64 1.5.1-2.fc24 @updates 236 k cronie-anacron x86_64 1.5.1-2.fc24 @updates 41 k crontabs noarch 1.11-12.20150630git.fc24 @koji-override-0 21 k crypto-utils x86_64 2.4.1-61.fc24 @fedora 176 k epson-inkjet-printer-artisan-725-835-series x86_64 1.0.0-1lsb3.2 @@commandline 3.1 M google-chrome-stable x86_64 53.0.2785.116-1 @google-chrome 181 M logwatch noarch 7.4.3-2.fc24 @fedora 1.9 M redhat-lsb x86_64 4.1-32.fc24 @fedora 0 redhat-lsb-core x86_64 4.1-32.fc24 @fedora 45 k redhat-lsb-cxx x86_64 4.1-32.fc24 @fedora 0 redhat-lsb-desktop x86_64 4.1-32.fc24 @fedora 0 redhat-lsb-languages x86_64 4.1-32.fc24 @fedora 814 redhat-lsb-printing x86_64 4.1-32.fc24 @fedora 0 webalizer x86_64 2.23_08-3.fc24 @fedora 349 k
Transaction Summary ================================================================================ Remove 20 Packages
Installed size: 260 M Is this ok [y/N]: n Operation aborted.
Why cronie depends on anacron, I have no idea, and I suspect all the other things being removed are because of cronie, but the only real alternative is to beat anacron with a big enough hammer. It can't be removed.
Hello,
It seems that we are experiencing different behaviours. It there any test that we could run to try to identify where the glitch is ?
By the way, nobody told me how to control anacron. The installation day can no be considered as a normal way to control an application !
In may opinion, we should have an independent control of crond and anacron ie. through /etc/crontab and /etc/anacontab
Regards.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com 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 11:49 PM From: "Jon LaBadie" jonfu@jgcomp.com To: users@lists.fedoraproject.org Subject: Re: cron
On Fri, Sep 23, 2016 at 09:23:43PM +0200, Patrick Dupre wrote:
From: "Jon LaBadie" jonfu@jgcomp.com On Fri, Sep 23, 2016 at 01:32:00PM +0200, Patrick Dupre wrote:
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 ?
why not USE CRON ?
Hello,
In fc22, anacron and crond where both running simultaneously fine. No any more in fc24 : it seems that now crond only run hourly and ignore the weekly (and daily) tasks. That I wish to restablish.
And I've noted several times in this thread that is not the case here. On my F24 system I have several crontabs, each with multiple entries. I also have things run by anacron from cron.daily, and cron.weekly. Further I have some things, like the locate database update being run by systemD timers.
Please consider that your F24 setup is incomplete or has some errors and your experience is not the norm.
Jon
Jon H. LaBadie jonfu@jgcomp.com _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On Sat, Sep 24, 2016 at 10:05:36AM +0200, Patrick Dupre wrote:
Hello,
It seems that we are experiencing different behaviours. It there any test that we could run to try to identify where the glitch is ?
By the way, nobody told me how to control anacron. The installation day can no be considered as a normal way to control an application !
UNTESTED!!
In /usr/share/anacron are 3 files (for monthly, weekly, daily) that each contain a single 8 char line (YYYYMMDD). These look like when each was run last. You could probably modify weekly to match your view of when weekly 'should' run.
In may opinion, we should have an independent control of crond and anacron ie. through /etc/crontab and /etc/anacontab
With just a few differences, then anacron and cron would be the same.
jl
Hello,
I modified the file /etc/anacrontab
to have the some of "delay in minutes" and RANDOM_DELAY less than 60 and it seems that it helps. At least cron run on saturday as expected
You mention 3 files in /usr/share/anacron
there are in /var/spool/anacron in my machine I am not sure that they control anything, maybe they monitor.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com 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: Saturday, September 24, 2016 at 8:23 PM From: "Jon LaBadie" jonfu@jgcomp.com To: users@lists.fedoraproject.org Subject: Re: cron
On Sat, Sep 24, 2016 at 10:05:36AM +0200, Patrick Dupre wrote:
Hello,
It seems that we are experiencing different behaviours. It there any test that we could run to try to identify where the glitch is ?
By the way, nobody told me how to control anacron. The installation day can no be considered as a normal way to control an application !
UNTESTED!!
In /usr/share/anacron are 3 files (for monthly, weekly, daily) that each contain a single 8 char line (YYYYMMDD). These look like when each was run last. You could probably modify weekly to match your view of when weekly 'should' run.
In may opinion, we should have an independent control of crond and anacron ie. through /etc/crontab and /etc/anacontab
With just a few differences, then anacron and cron would be the same.
jl
Jon H. LaBadie jonfu@jgcomp.com _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On 09/24/2016 12:02 PM, Patrick Dupre wrote:
You mention 3 files in /usr/share/anacron
there are in /var/spool/anacron in my machine I am not sure that they control anything, maybe they monitor.
Those are the timestamp files mentioned in the man page. They tell the program when it was last run.
-
Joe Zeff -
Jon LaBadie -
Matthew Miller -
Patrick Dupre -
Rick Stevens -
Samuel Sieb -
Tom Horsley