search for: anacrontab

Is one meant to have one or the other? If so, which is recommended? I have -------------------------------- [tim at helen etc]$ cat anacrontab # /etc/anacrontab: configuration file for anacron # See anacron(8) and anacrontab(5) for details. SHELL=/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root 1 65 cron.daily run-parts /etc/cron.daily 7 70 cron.weekly run-parts /etc/cron.weekly 30...

...d out of /etc/crontab, /etc/cron.daily, etc. or user-level crontabs? The "mailto" value is crontab file specific, so setting it in /etc/crontab would only effect commands run from there (a file that isn't used much any longer). As the /etc/cron.daily, etc. jobs are now run from /etc/anacrontab you'd need to adjust the "mailto" in that file for things run that way. If run from a user-level crontab the "mailto" needs to be in that user's crontab file. [cron.hourly is run out of /etc/cron.d/0hourly, not anacrontab, and has its own "mailto".]

...d. So how could stuff in /etc/cron.{daily,weekly} work until June 02? Probably because it didn't need anacron at all, no? I've looked at yum history, it doesn't talk at all about anacron (but cronie-anacron) so it's not been installed and removed). > It's configured in /etc/anacrontab and is usually run once a day by the > script /etc/cron.hourly/0anacron - cron.hourly is still run by cron. > If the script doesn't exist, then anacron won't run and cron.daily etc > won't happen. There's a /etc/cron.d/0hourly here: ------------- # Run the hourly jobs SHE...

Hi, I just configured SquidAnalyzer, a nifty little network statistics tool that I'm using mainly in school networks to monitor network usage. I want to run the '/usr/bin/squid-analyzer' script once a day. I took a peek in /etc/cron.daily, and the package already installed an /etc/cron.daily/0squidanalyzer script. I wanted to know at what time CentOS ran the cron.daily scripts,

Hi all, I wanted to schedule some rsync backups and found that CentOS is by default using anacron. I'm mostly used with the historical cron, but let's follow the progress :-) - I made a shell script in /etc/cron.daily/dobackup - I made it 755, root.root. - In /etc/anacrontab, START_HOURS_RANGE=21-23 (I kept the other lines unchanged) - When I manually run /etc/cron.daily/dobackup, it runs quietly (no errors) Where should I check if the task scheduler is setup correctly (logs)? Must I reload a service (BTW, is it "crond" yet?) after editing /etc/anacrontab...

Well, I feel silly.? There are three places MAILTO can affect crond: /etc/crontab, /etc/crond.d/0hourly, and /etc/anacrontab.? Once I set this in these 3 files, I started getting mail from crond.? Thank you all for your help. --- Chad Cordero Information Technology Consultant Enterprise & Cloud Services Information Technology Services California State University, San Bernardino 5500 University Pkwy San Bernar...

> > So, service is running but what could happen that makes /etc/cron.* not > being fired? You don't say, but if this is CentOS 7, then cron.daily/weekly/monthly is run using anacron, not cron. It's configured in /etc/anacrontab and is usually run once a day by the script /etc/cron.hourly/0anacron - cron.hourly is still run by cron. If the script doesn't exist, then anacron won't run and cron.daily etc won't happen. P.

...not installed. So how could stuff in /etc/cron.{daily,weekly} > work until June 02? Don't know. But that's how cron.daily is processed and has been since CentOS7 was released. In fact I think CentOS 6 even used anacron. Perhaps you have inadvertently removed an important file like /etc/anacrontab or /etc/cron.hourly/0anacron > Probably because it didn't need anacron at all, no? I've looked at yum > history, it doesn't talk at all about anacron (but cronie-anacron) so > it's not been installed and removed). Yes, anacron *is* cronie-anacron > > > > It...

...ron.daily, etc. or user-level > crontabs? > > The "mailto" value is crontab file specific, so setting it in > /etc/crontab would only effect commands run from there (a file that > isn't used much any longer). As the /etc/cron.daily, etc. jobs are > now run from /etc/anacrontab you'd need to adjust the "mailto" in > that file for things run that way. If run from a user-level crontab > the "mailto" needs to be in that user's crontab file. [cron.hourly is > run out of /etc/cron.d/0hourly, not anacrontab, and has its own > "mailto...

...essage and the next message is at 03:57:57 ? there are always >> messages like around the time when the daemon dies. What could be >> going on here? > > > Have you checked /etc/cron.daily/ for a cron job to restart the pure-ftpd > service? /etc/cron.daily is called from /etc/anacrontab with some randomness > so that the execution time varies. I will check that, but the the pure-ftpd service is not my daemon that is getting killed - I was thinking the sudden stopping of the logging and subsequent time gap would be some sort of clue as to what is happing at that time. This is...

Hello there, I've just noticed that scripts in /etc/cron.{daily,weekly,...} are not launched for several weeks (I noticed a `locate` not finding a recently added binary). Exactly, it's since June 02, and `# service cron status` says: Redirecting to /bin/systemctl status crond.service * crond.service - Command Scheduler Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled;

I have a CentOS 7 system that I run a home grown python daemon on. I run this same daemon on many other systems without any incident. On this one system the daemon seems to die or be killed every day around 3:30am. There is nothing it its log or any system logs that tell me why it dies. However in /var/log/messages every day I see something like this: May 10 03:35:58 localhost pure-ftpd: (tool at

It?s being rejected before it even reaches the mailbox, so forwarding won?t work.? Crond should really be using the MAILTO variable and it?s not. --- Chad Cordero Information Technology Consultant Enterprise & Cloud Services Information Technology Services California State University, San Bernardino 5500 University Pkwy San Bernardino, CA 92407-2393 Main Line: 909/537-7677 Direct

...58 is truncated > mid-message and the next message is at 03:57:57 ? there are always > messages like around the time when the daemon dies. What could be > going on here? Have you checked /etc/cron.daily/ for a cron job to restart the pure-ftpd service? /etc/cron.daily is called from /etc/anacrontab with some randomness so that the execution time varies. Alexander

...a scheduler. It *aims at replacing Vixie Cron*, so it implements most of its functionalities. But contrary to Vixie Cron, fcron *does not need your system to be up 7 days a week, 24 hours a day* : it also works well with systems which are not running neither all the time nor regularly (contrary to anacrontab). In other words, fcron does both the job of Vixie Cron and anacron, but does even more and better :)) ... Any clue, Regards, Kaushal

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;

Hi, Up until now I always kept my servers up-to-date manually. Currently I'm experimenting with yum-cron to automate this process. I read through various online tutorials, and now I have a couple questions. 1. As far as I know, when editing /etc/yum/yum-cron.conf, I can only use the following value for update_cmd : update_cmd = default If I understand this correctly, 'update_cmd =