On Wed, Nov 20, 2002 at 11:20:32AM +1000, [EMAIL PROTECTED] wrote:
> /etc/crontab has an extra field? I didn't notice it from what was already
> there...
Yes, compared to a user's crontab.
> 01 * * * * root nice -n 19 run-parts /etc/cron.hourly
^^^^
Note the username. This doesn't appear in a user's crontab
> 02 4 * * * root nice -n 19 run-parts /etc/cron.daily
> 22 4 * * 0 root nice -n 19 run-parts /etc/cron.weekly
> 42 4 1 * * root nice -n 19 run-parts /etc/cron.monthly
>
> # Perform a full backup every sunday at 7.30pm
> 30 7 * * sun /root/full-backup.sh >>/var/log/backups 2>&1
>
> # Perform an incremental backup at 7.30pm every weekday and saturdays.
> 30 7 * * mon-sat /root/incr-backup.sh >>/var/log/backups 2>&1
You left out the username. You should see an error message in
/var/spool/cron.
> `ps x` tells me that crond is running. Does it need to be restarted when
> /etc/crontab is modified?
No.
> (How often does crond read /etc/crontab?)
Once a minute. From cron(8):
Additionally, cron checks each minute to see if its spool
directory's modtime (or the modtime on /etc/crontab) has changed,
and if it has, cron will then examine the modtime on all crontabs
and reload those which have changed. Thus cron need not be
restarted whenever a crontab file is mod- ified. Note that the
Crontab(1) command updates the mod- time of the spool directory
whenever it changes a crontab.
Cheers,
John
--
whois [EMAIL PROTECTED]
GPG key id: 0xD59C360F
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
