I really get annoyed when inaccurate info gets disseminated. It tends to
flourish.
crontabs do not live, mostly, in /etc/crontab. That directory is a feature
of Linux cron. The plave where crontabs live is /var/spool/cron. There you
will find one file for each user who has a crontab. /etc/crontab/* is a
convenience created for the sysadm.
In addition, the cron under linux does *not* need a SIGHUP to know when
something has changed.
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.
Crontabs are in a directory, mostly /etc/cron.* (daily, hourly)
In /etc/crontab the exact directory is given, and an interval is given to
execute all files in the directory.
If the new crontab is one of the excisting, just add in the apropriate
directory, or add an new entry to /etc/crontab.
To let cron reread the config file, just send it an HUP.
Igmar
-Time flies like the wind. Fruit flies like a banana. [EMAIL PROTECTED]
-Stranger things have happened but none stranger than this. Steven W. Orr-
Does your driver's license say Organ Donor?Black holes are where God \
-------divided by zero. Listen to me! We are all individuals!---------
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
