On Mon, 2006-02-20 at 13:21 -0600, Johnny Hughes wrote: > On Mon, 2006-02-20 at 13:12 -0600, 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 ago tho soooo...here's the crontab: > > 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 > > 05 * * * * /usr/bin/freshclam > > # > > 11 0,4,8,12,16,20 * * * root /usr/bu-snap/bu-snap.sh > /dev/null 2>&1 > > > > I have another box running bu-snap.sh in the same kinda crontab setup. > > Only diff. is that box is a 64bit and this 32...both 4.2 sys. > > > > In the other box...bu-snap is logging in var/log/messages as it's > > supposed to the time it starts and the time it finishes...and the > > results show working fine. In this latest installed system...I just > > can't get it to run under this crontab. should run at hr:11 every 4 hrs. > > > > thx > > > > John Rose > > > > make sure crond is running and set to start on bootup. > > service crond status > > and > > chkconfig --list crond > if there is any kind of problem, where it cannot complete it's job(bu- snap.sh) it does msg me. ...no msgs from it. oh ya...crond is running and /var/log/messages and cron are plum full or crond input. bu-snap.sh writes to ../log/messages when it starts and when it finishes... but in this box, says nothing and, of course, it doesn't even run as I can tell. this sucker has me stumped... and also...lots of other stuff in the logs of chrond running root stuff so it's not a problem of not running root stuff. thx jr > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos