The actual crontab file for a given user has a warning
about not editing it directly. When you use crontab -e, the
application takes care of installing the new crontab for the
user and appears to do a kill -HUP on cron to get it to load the
new crontab for that user.
Suppose one wants to run a particular crontab while on
vacation or during some other unusual time period and then switch
back to a "normal" crontab. Is it safe to make at cp a new
version of crontab to /var/spool/crontabs/user and then do a KILL
-HUP on cron's PID?
I want to properly duplicate what the crontab -e
application does and not introduce some problem that bites later.
Thanks for any thoughts.
Martin McCormick WB5AGZ Stillwater, OK
Systems Engineer
OSU Information Technology Department Network Operations Group
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
