Greetings,
Per the subject line, what controls the time of the running of scripts located in the /etc/cron.[daily|weekly|hourly] directories?
Specifically with CentOS 6.* I've noticed that scripts in /etc/cron.daily and /etc/cron.weekly run at different times of the day, or on different days. In my experience on other rpm-based distributions, cron daily and weekly scripts run at 4am; those that are run weekly run at 4am on Sunday morning.
Much thanks in advance,
Max Pyziur pyz@brama.com
From: Max Pyziur pyz@brama.com
Per the subject line, what controls the time of the running of scripts located in the /etc/cron.[daily|weekly|hourly] directories?
Specifically with CentOS 6.* I've noticed that scripts in /etc/cron.daily and /etc/cron.weekly run at different times of the day, or on different days. In my experience on other rpm-based distributions, cron daily and weekly scripts run at 4am; those that are run weekly run at 4am on Sunday morning.
Seems like there is some info in: man anacrontab
JD
On Fri, 29 Mar 2013, John Doe wrote:
From: Max Pyziur pyz@brama.com
Per the subject line, what controls the time of the running of scripts located in the /etc/cron.[daily|weekly|hourly] directories?
Specifically with CentOS 6.* I've noticed that scripts in /etc/cron.daily and /etc/cron.weekly run at different times of the day, or on different days. In my experience on other rpm-based distributions, cron daily and weekly scripts run at 4am; those that are run weekly run at 4am on Sunday morning.
Seems like there is some info in: man anacrontab
Greetings,
Much thanks to all for the replies. I now understand the logic of what is happening (I'm a two CentOS server, three Fedora desk/laptop person, myself; I do SQL and other things for food, not sysadmin). Having acclimated to precise delivery of sysadmin-related reports (logwatch, rkhunter, etc) showing timestamps of 4am (or thereabouts), I was caught by surprise after making a necessary move from CentOS 5 to CentOS 6, with what appeared to be erratic delivery of cron.daily-/cron.weekly-driven sysadmin reporting.
Thanks again, more questions soon.
JD
MP pyz@brama.com
On 2013-03-29, Max Pyziur pyz@brama.com wrote:
Much thanks to all for the replies. I now understand the logic of what is= =20 happening (I'm a two CentOS server, three Fedora desk/laptop person,=20 myself; I do SQL and other things for food, not sysadmin). Having=20 acclimated to precise delivery of sysadmin-related reports=20 (logwatch, rkhunter, etc) showing timestamps of 4am (or thereabouts), I=20 was caught by surprise after making a necessary move from CentOS 5 to=20 CentOS 6, with what appeared to be erratic delivery of=20 cron.daily-/cron.weekly-driven sysadmin reporting.
If you prefer this style, you can remove anacron. If you do that, you may wish to install the cronie-noanacron package to restore the running of periodic jobs out of the daily/weekly/monthly directories.
--keith
-
John Doe -
Keith Keller -
Max Pyziur