Date: Sun, 5 Apr 1998 13:36:04 -0400 (EDT) From: jack <jack@germanium.xtalwind.net> To: Harry Patterson <harry@visiontm.com> Cc: sfarrell+list@farrell.org, freebsd-questions <freebsd-questions@FreeBSD.ORG> Subject: Re: crontab problems Message-ID: <Pine.BSF.3.96.980405133127.1542A-100000@germanium.xtalwind.net> In-Reply-To: <01bd60b3$f22a1aa0$f46190cf@hp.harry.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 5 Apr 1998, Harry Patterson wrote:
> For the system crontab (using your numbering):
>
> [1] DO NOT crontab crontab from root to activate the system crontab. This
> will only activate a crontab for the root user not the system crontab.
>
> [2] edit /etc/crontab and restart the cron process (ie. kill -1 PID).
> /etc/crontab is the system crontab and loads when cron is started.
>
> If I'm wrong please correct me, otherwise thanks again.
RTFM :) 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 modified. ^^^^
^^^^^^^^^^^^^^^^
SEE ALSO
crontab(1), crontab(5)
--------------------------------------------------------------------------
Jack O'Neill Systems Administrator / Systems Analyst
jack@germanium.xtalwind.net Crystal Wind Communications, Inc.
Finger jack@germanium.xtalwind.net for my PGP key.
PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD
enriched, vcard, HTML messages > /dev/null
--------------------------------------------------------------------------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980405133127.1542A-100000>