Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-unix!quintus!sun!pitstop!sundc!seismo!uunet!mcvax!ukc!stc!ist!uel!andrew
From: andrew@uel.uel.co.uk (Andrew Josey)
Newsgroups: comp.unix.questions
Subject: Re: Cron
Summary: cron only examines crontab files when cron starts or if file changes
	 via the crontab(1) or at(1) commands
Message-ID: <712@uel.uel.co.uk>
Date: 29 Jan 88 09:04:11 GMT
References: <235014@<1988Jan17> <10800014@bradley>
Organization: AT&T Unix Europe, London, UK
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. 

As of System V Release 2 and later, the crontab(1) command must be
ran to force cron to examine the appropriate file. This reduces the
overheads in checking for new or changed files at regular intervals.
See cron(1M).
-- 
 Andrew Josey,	AT&T Unix Europe, a Division of AT&T (UK) Ltd.
 International House, Ealing Broadway, London W5 5DB, England, UK
 uucp:{ mcvax!ukc, attunix} uel!andrew
 { The usual disclaimer .... }