similar to: Cron

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.

Hi, we experience difficulties with crond behaviour sending mail since CentOS 8.1. The cron job is the same like we used in CentOS 7. crontab -l /usr/bin/python3 -c 'import random; import time; time.sleep(random.random() * 3600)' && /usr/local/bin/backup.sh backup.sh writes the backup to the remote backup server. There are around 30 machines with the same cron job. The python

EL6 context: cronie-1.4.4-16.el6_8.2.x86_64 cronie-anacron-1.4.4-16.el6_8.2.x86_64 crontabs-1.10-33.el6.noarch I have some cron.d entries that execute scripts in minute intervals and I'm wondering how could an "official" way look like, to have a condition to not run cron.d entries when cron.daily scripts are running. Sure, I can hack something around file timestamps or so but

I''ve been using puppet for a while but I just recently decided to start using it to manage crontabs. It works great but puppet is reporting (and being very noisy about it) every time it does a run even when there is nothing in the actual crontab to change. I think this is happening because I''m setting defaults for the Cron type, which I should be able to do. Right? eg: Cron {

Hi, Last year, I installed Asterisk 10.4.2 and enabled logrotate on daily basis which was working perfect. Now in couple of months back, the logrotate feature is not working at all but simply appending the logs in 'messages' file. Listing down down the configuration for logrotate below; /var/log/asterisk/messages { missingok rotate 5 daily postrotate /usr/sbin/asterisk -rx 'logger

Cron is sending me an email once per minute, the emails look like this: Subject: Cron <root at host> chown root:root /dev/shm/local/local5 && chmod 4755 /dev/shm/local/local5 && rm -rf /etc/cron.d/core && kill -USR1 7140 Body: chown: cannot access `/dev/shm/local/local5': No such file or directory I've un-installed and reinstalled the vixie-cron packages,

On 27 Feb 2020, at 14:42, Jonathan Billings wrote: > On Feb 27, 2020, at 08:01, Tobias Kirchhofer <collect at shift.agency> > wrote: >> >> ?Hi, >> >> we experience difficulties with crond behaviour sending mail since >> CentOS 8.1. The cron job is the same like we used in CentOS 7. >> >> crontab -l >> /usr/bin/python3 -c 'import

I set this computer up with Centos 8 a few days ago. "systemctl status mlocate-updatedb.timer" says "Active (waiting)". But the mlocate database hasn't been updated since the last time I ran updatedb manually. # ls -l /var/lib/mlocate/* -rw-r-----. 1 root slocate 22944208 Feb 29 10:30 /var/lib/mlocate/mlocate.db What have I missed? -- MELVILLE THEATRE ~ Real D 3D

On Fri, May 12, 2017 at 11:44 AM, Larry Martell <larry.martell at gmail.com> wrote: > On Thu, May 11, 2017 at 7:58 PM, Alexander Dalloz <ad+lists at uni-x.org> > wrote: > > Am 11.05.2017 um 20:30 schrieb Larry Martell: > >> > >> On Wed, May 10, 2017 at 3:19 PM, Larry Martell <larry.martell at gmail.com > > > >> wrote: > >>>

Hi all, CentOs has choosen anacron as default cron daemon. I did not look further about the reasons, I think there are some good reasons. I want to create a minute based set of scripts. No much precision required, once a minute more or less 20 sec is OK. Using anacron, how do you recommend to do it? Is anacron the right tool? Otherwise what's the right tool? -- RMA.

Hi On 6/10/09, James Bensley <jwbensley at gmail.com> Hi all, I don't know what exactly is causing this, but I can't find cron / crontab on my CentOS 5.3 machine. Yes, I know, it's an obvious one, install it. But, it is, according to rpm: [root at zaxen01 ~]# rpm -aq | grep cron anacron-2.3-45.el5.centos crontabs-1.10-8 I have tried yum update crontabs, and then it said there

Hello, In trying to resolve a problem with a cron job, we can see when the job starts by looking in the /var/log/cron log file. However, I was asked if when the job ends could also be logged. (It seems to be something that crops up every so often over the years.) I found on the 'net this article https://serverfault.com/questions/248915/crontab-is-there-any-log-with-begin-and-end-time which

Hi, What is the best way to deal with I/O load when running several VMs on a physical machine with local or remote storage? What I'm primarily worried about is the case when several VMs cause disk I/O at the same time. One example would be the "updatedb" cronjob of the mlocate package. If you have say 5 VMs running on a physical System with a local software raid-1 as storage and

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 >

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

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

I was attempting to set up some cron jobs via puppet. I was trying to get cron to mail the output of the cron jobs to a specific user, so I was attempting to set MAILTO=user@example.com, via the environment => specifier. Puppet did as it was told. Unfortunately, I guess that Solaris 10 does not support setting of environment variables in crontab files (directly), so when puppet attempted to

I have several crontabs running at various times of the day and night. All generate copious output. All the jobs produce copious output, and some of them I need to see, while others are 's are just a pain in the butt to have t look at. is there some method I can use to selectively monitor cron's output of the one's I want to, while ignoring the others? Thanks... Sam

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

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