Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
For whatever reason, on most Linux distros cron.daily is run at 3-4am. Generally I move it back to midnight, but on CentOS 6.2 I cannot for the life of me figure out where it's configured!
The /etc/crontab does not have cron.daily listed, and grepping for it in /etc returns no useful results.
It appears they made a change in 6 so that daily, hourly, weekly etc... are run in anacron rather than cron so as to avoid conflict with cron. The file you need is /etc/anacrontab
I figured this out by reviewing /etc/crontab which gave standard crontab line (as used in user crontabs that is) examples but was otherwise empty. It noted:
Quote:
# For details see man 4 crontabs
Typing "man 4 crontabs" gave the man page which says in part:
Quote:
Historically the crontab file contained configuration which called run-parts on files in cron.{daily,weekly,monthly} directories. These jobs are now run indirectly through anacron to prevent conflicts between cron and anacron. That means the anacron package has to be installed if the jobs in these directories should be running. Refer to the anacron(8) how to limit the time of day of the job execution.
Typing "man anacron" gave the man page which says in part:
Quote:
Anacron reads a list of jobs from a configuration file, /etc/anacrontab (see anacrontab(5)). This file contains the list of jobs that Anacron controls. Each job entry specifies a period in days, a delay in minutes, a unique job dentifier, and a shell command.
When I looked at /etc/anacrontab I saw at the end of the file:
Code:
#period in days delay in minutes job-identifier command
1 5 cron.daily nice run-parts /etc/cron.daily
7 25 cron.weekly nice run-parts /etc/cron.weekly
@monthly 45 cron.monthly nice run-parts /etc/cron.monthly
Based on your info, I discovered that you need to add "cronie-noanacron" and erase "cronie-anacron" to get the old behavior of setting cron.daily start times.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.