Path: utzoo!mnetor!uunet!mcvax!ukc!stl!stc!root44!njh
From: njh@root.co.uk (Nigel Horne)
Newsgroups: comp.unix.questions
Subject: Re: Cron
Message-ID: <548@root44.co.uk>
Date: 23 Feb 88 16:55:06 GMT
References: <235014@<1988Jan17> <10800014@bradley>
Reply-To: njh@root44.UUCP (Nigel Horne)
Organization: UniSoft Ltd., London, England
Lines: 15

In article <10800014@bradley> brad@bradley.UUCP writes:
>We have a 3b5 here (actually more than 1), that when a change is
>made /usr/spool/cron/crontabs /etc/cron doesn't pick up the change
>and the only way was to kill cron and restart it.

Actually there's no need to do that. You should change your crontab file
using the crontab(1) command rather than by hand. This command will also
"tell" cron that your file has been ammended and that it should reread.

-Nigel
-- 
--
Nigel Horne, Director of Quality and Programmes, UniSoft Ltd.
<njh@root.co.uk>	G1ITH	Fax:	(01) 726 2750
Phone:	+44 1 606 7799 Telex:	885995 UNISFT G	BT Gold: CQQ173