CentOS - Feb 2006 - crontab problems

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

On Mon, 2006-02-20 at 20:41 +0000, ABOKHALAF, Nassri Abdellatif
wrote:
> 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 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
> > > #
The redhad admin doc says you don't have to restart crond after making
changes because it runs every minute although I have done a restart on
it many times.