Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!cuuxb!ltuxa!ll1a!nesac2!jec
From: jec@nesac2.UUCP (John Carter ATLN SADM)
Newsgroups: comp.unix.questions
Subject: Re: Cron
Summary: have to kill cron?
Message-ID: <940@nesac2.UUCP>
Date: 28 Jan 88 21:23:26 GMT
References: <235014@<1988Jan17> <10800014@bradley>
Organization: A.T.&T. Lisle, Ill.
Lines: 18
Posted: Thu Jan 28 16:23:26 1988

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. 

Was I the only recipient of the information that you can get cron to
accept new data in a particular crontab file by:
1) cd /usr/spool/cron/crontabs
1a) cp root root.bk  (skip this if you never make mistakes :-)
2) ed root
3) make changes, write, quit
4) crontab root
5) cd back_to_where_you_started
-- 
USnail: John Carter, AT&T, Atlanta RWC, 3001 Cobb Parkway, Atlanta GA 30339
Video:	...ihnp4!cuea2!ltuxa!ll1!nesac2!jec    Voice: 404+951-4642
(The above views are my very own. How dare you question them? :-)