Scott Gifford <[EMAIL PROTECTED]> writes:
> Martin McCormick <[EMAIL PROTECTED]> writes:
> You can install a crontab file by running:
>
> crontab [filename]
When you create the file for crontab, don't forget the warning found in
the crontab man page:
"Although cron requires that each entr
Martin McCormick <[EMAIL PROTECTED]> writes:
[...]
> I want to properly duplicate what the crontab -e
> application does and not introduce some problem that bites later.
You can install a crontab file by running:
crontab [filename]
This will do exactly what crontab -e does, only with
martin f krafft writes:
> If you can ensure that there are no syntax errors in the file you
> install manually, then yes, it should be safe. The reason why this
> note is there is because crontab does syntax checks on the
> user-submitted file.
Great! Thanks. To ask if I can insure there
also sprach Martin McCormick <[EMAIL PROTECTED]> [2006.09.01.2258 +0200]:
> 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
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 w
5 matches
Mail list logo
