similar to: Crontab not working....

Crontab offers many refined facilities for Western calendaring, but none for traditional Eastern-- lunar-- designations. So for example, if one wants specify regular occurring events on full moons or on new moons, there is no way to do this. Emacs (a text processor!?) accomplishes this. The math for calculating lunar calendaring is already available; mathematical functions are already

Hi, I have a strange problem here. I have two servers, one dedicated webserver, and a local backup server. On the webserver I have this : [root at 12569hpv163154:~] # crontab -l 00 22 * * * /usr/local/bin/sauvegarde-pmbccps.sh This launches a backup script every day at 22:00, and it works as expected. Now here's what I have on the local backup server : [root at grossebertha:~] # crontab

Hiya, Currently running Centos 4.2 x86_64 dist on a dual 3G xeon, 2G ram, scsi setupand everythings been running fine on it for some time. Then at 4am last night something kicked in (have mrtg running monitoring when) and since then its been running a load of about 1.5 (normally around 0.4). CPU usage is Cpu(s): 1.1% us, 0.6% sy, 0.0% ni, 97.9% id, 0.2% wa, 0.1% hi, 0.1%si. Can't see

----- KSR[T] Website : http://www.dec.net/ksrt E-mail: ksrt@dec.net ----- KSR[T] Advisory #005 Date: Dec 6, 1997 ID #: lin-dcrn-005 Operating System(s): Slackware 3.4 Affected Program: dillon crontab / crond ( dcron

Hiya, just wondering how easy this would be, I'm guessing through yum, but is there a preferable process from updating from fed core 3 to centos ideally keeping settings as is? (desktop rather than server, just want to migrate to centos, nothing too essential apart from raw data). Ian

On 5 Apr 2020, at 21:20, Tobias Kirchhofer wrote: >>>> we experience difficulties with crond behaviour sending mail since >>>> CentOS 8.1. The cron job is the same like we used in CentOS 7. > > Meanwhile we found the reason for the bug - actually we do not know if > it is related to a specific version of CentOS or a specific kind of > command as cron job.

Hi, I've installed CentOS-4 4 days ago. Now, every 5 minutes, crond opens and close a root session, with no other info. Example: Apr 14 16:25:01 tux crond(pam_unix)[4031]: session opened for user root by (uid=0) Apr 14 16:25:02 tux crond(pam_unix)[4031]: session closed for user root Every five minutes the same thing. I have nothing in /etc/crontab that makes such a thing. Does anyone

hello list!! I'm attempting to find out why this cron job isn't running. the host is centos 5.6 on i386 just so you know. 0 3 * * * /bin/alldb > /home/bluethundr/backupdb/alldb-$(date +%Y%m%d%H%S).sql The job is meant to backup all the databases on a mysql server every day at 3 am. I have checked the backup directory and nothing is showing up for those

greetings on a simple CentOS 4 DNS server install i have the below info. crontab -l "shows nothing" pico /etc/crontab shows... SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root HOME=/ # run-parts 01 * * * * root run-parts /etc/cron.hourly 02 4 * * * root run-parts /etc/cron.daily 22 4 * * 0 root run-parts /etc/cron.weekly 42 4 1 * * root run-parts /etc/cron.monthly i

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

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

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.

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

On Tue, Oct 13, 2015 at 1:58 PM, Richard <lists-centos at listmail.innovate.net> wrote: > > >> Date: Tuesday, October 13, 2015 13:54:28 +0000 >> From: "C. L. Martinez" <carlopmart at gmail.com> >> >> On Tue, Oct 13, 2015 at 1:45 PM, Richard >> <lists-centos at listmail.innovate.net> wrote: >>> >>>> Date: Tuesday,

On Tue, Oct 13, 2015 at 2:35 PM, Jonathan Billings <billings at negate.org> wrote: > On Tue, Oct 13, 2015 at 02:04:49PM +0000, C. L. Martinez wrote: >> And according to systemd, without problems: >> >> crond.service - Command Scheduler >> Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled) >> Active: active (running) since Tue 2015-10-13

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

Dear All Please be informed that I have an CentOS 5 server and I need it to be automatically rebooted at pre-specified times . To this end , I tried to set it as its crontab job as the followings : #crontab -e 30 15 * * * reboot It got through but after the server first reboot the crontab job disappeared . So I tried to set it in another way , as the followings : set the cron list in /tmp/temp add

Did you restart the crontab service after the change ? If not, crontab wont be aware of the changes. Nassri > rado wrote: > > for some reason, crontab is not picking up a job here > listed. I, for > > one see nothing wrong w/it as I have been running approx the same > > basic crontab for well over a year now. I have just put this box on > > line about a week

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

On 12/06/2015 02:23 AM, ken wrote: > Crontab offers many refined facilities for Western calendaring, but none > for traditional Eastern-- lunar-- designations. So for example, if one > wants specify regular occurring events on full moons or on new moons, > there is no way to do this. Emacs (a text processor!?) accomplishes > this. The math for calculating lunar calendaring is