similar to: Tasks in /etc/cron.daily on CentOS 7?

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;

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

Hello Pete, On Mon, 02 Jul 2018 09:59:17 +0100 Pete Biggs <pete at biggs.org.uk> wrote: > > > > 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. Oops, yes CentOS 7, sorry. For the record: # service anacron

> > 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

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 =

> Date: Thursday, July 20, 2017 02:25:52 +0000 > From: Richard <lists-centos at listmail.innovate.net> > >> Date: Wednesday, July 19, 2017 23:31:10 +0000 >> From: Chad Cordero <ccordero at csusb.edu> >> >> It?s being rejected before it even reaches the mailbox, so >> forwarding won?t work.? Crond should really be using the MAILTO >>

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

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

I made a script to backup a folder on a remote server it works manually, I set a cron job to launch the script every 2 mins (for test), I sse in the log this line Mar 13 13:10:01 debian /USR/SBIN/CRON[6302]: (root) CMD (root /usr/bin/backup.sh) but when I sheck the remote server nothing is done, any sugestions pls

Hi all. Can anyone help me with scheduling tasks? I'm running Centos4.2 (updated via yum starting from 4.0). I know I have vixie-cron and anacron packages installed (came like that, from first install, I guess). I read the crontab syntax man page (man 5 crontab) and I made an entry as a normal user (using crontab -e) that looks like the following: 30 0 9 1 1 /bin/ls -F /home/jose >

Hi all I have a '/etc/cron.daily/push-to-backup' script which the content is: #!/bin/bash /usr/bin/rsync [... long options line ...] echo "finished pushing to the backup" Launched manually, it's OK. Waiting for cron to execute it, In the "/var/log/cron", I see the starting time and the finish time, and I see it take about 10 minutes to make the job.

For some reason I cannot fathom, cron.hourly runs twice each hour on one of my two CentOS-5.4 systems, as reported in /var/log/cron: ------------------------- Mar 16 14:01:01 helen crond[27833]: (root) CMD (run-parts /etc/cron.hourly) Mar 16 14:01:01 helen crond[27834]: (root) CMD (run-parts /etc/cron.hourly) ------------------------- On the other it just runs once, as expected.

Hi all, Who takes care of cronjob in /etc/cron.d ? Should we tell crond to run it? /etc/crontab only mentions hourly, daily, weekly, monthly -- Thanks Fajar

Hi, I'm using the SquidAnalyzer network analysis tool in combination with Squid. Up until now, I've been running Slackware Linux on my servers. I built a custom package that installs SquidAnalyzer to /var/www/vhosts/squidreport/html. Then I setup an Apache virtual host for SquidAnalyzer's pages. Since I'm migrating my servers from Slackware to CentOS, I'd like to build a

zep wrote: > On 10/13/2015 09:54 AM, C. L. Martinez wrote: >> I haven't entries in conrtab's users file at this moment, but I have >> done a test: * * * * * ls -la, and it is not triggered. But like I say >> before, installed system cronjobs like logwatch task are not triggered > > I'd say that crontab doesn't actually prove that the job isn't being

What is the ramifications to simply placing scripts in the /etc/cron.hourly directory as opposed to actually adding jobs via the crontab -e method? Is there any significance to using one method versus the other? Thanks! jlc

> > For the record: > # service anacron status > Redirecting to /bin/systemctl status anacron.service > Unit anacron.service could not be found. > You have mail in /var/spool/mail/root It's not a service. As I said, it's run using a script in /etc/cron.hourly > > Sure, anacron is not installed. So how could stuff in /etc/cron.{daily,weekly} > work until June

Hi, I have to setup a scheduled task on a server, and I just read through some crontab docs. Now I'm confused. It's not so much the syntax of the cron job to define (I got that), it's more... how do I get to define it? Use a text editor (vi or the likes) to edit /etc/crontab directly? Or create some empty file in /etc/cron.daily or /etc/cron.hourly or the likes and then edit it

hey centos long time no hear! :) I'm having a small issue where the backup jobs that I set to run in the crontab of the backup user do not appear to be running. Here's how I set it up (with crontab -e as the backup user): run amanda every night (check at 2:45 and backup at 3) 45 2 * * * /usr/sbin/amcheck /var/log/amanda/crontab/amcheck.log * 3 * * * /usr/sbin/amdump

Hi All, is it possible to delete cronjobs by patterns using ''cron'' resource? I.e. I want to make sure that there is no any cronjob that contains "/ path/to/some/unneeded_file" command in root crontab without knowing the command possible parameters and schedule. If no, any suggestions about how it can be performed are welcome. Thanks in advance