Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/3/85; site ukecc.UUCP
Path: utzoo!watmath!clyde!cbosgd!ukma!ukecc!edward
From: edward@ukecc.UUCP (Edward C. Bennett)
Newsgroups: net.unix
Subject: Re: Re: crontab: Sunday=7, not 0.
Message-ID: <324@ukecc.UUCP>
Date: Mon, 18-Nov-85 17:54:50 EST
Article-I.D.: ukecc.324
Posted: Mon Nov 18 17:54:50 1985
Date-Received: Wed, 20-Nov-85 00:18:31 EST
References: <704@adobe.UUCP> <187@l5.uucp> <491@ttidcb.UUCP> <2935@sun.uucp> <573@kitty.UUCP>
Organization: Univ. of Ky. Engineering Computing Center
Lines: 17

In article <573@kitty.UUCP>, larry@kitty.UUCP (Larry Lippman) writes:
> 	My question: does anyone know why simply editing the particular crontab
> file will not work, and why the crontab command MUST be used?
> 
> ===  Larry Lippman @ Recognition Research Corp., Clarence, New York        ===

	On our 3B20 we found that the only way to get cron to reread
/usr/spool/cron/crontabs/* was to kill and restart /etc/cron.

-- 
Edward C. Bennett

UUCP: ihnp4!cbosgd!ukma!ukecc!edward

/* A charter member of the Scooter bunch */

"Goodnight M.A."