Path: utzoo!utgpu!water!watmath!clyde!rutgers!mit-eddie!husc6!cmcl2!nrl-cmf!ames!pasteur!ucbvax!sdcsvax!ucsdhub!esosun!seismo!uunet!mcvax!rivm!ccea3
From: ccea3@rivm.UUCP (Adri Verhoef)
Newsgroups: comp.unix.questions
Subject: Re: Cron
Message-ID: <650@rivm05.UUCP>
Date: 23 Jan 88 02:57:42 GMT
References: <11098@brl-adm.ARPA> <449@wa3wbu.UUCP> <1988Jan17.235014.19530@lsuc.uucp> <3000@killer.UUCP>
Reply-To: ccea3@rivm05.UUCP (Adri Verhoef)
Organization: RIVM, Bilthoven, The Netherlands
Lines: 8

In article <3000@killer.UUCP> jfh@killer.UUCP (John Haugh) writes:
>The NEW cron's have individual crontabs for each (potential) user.  Editing
>one of those files will not update cron's idea of what is going on.  You
>must use the crontab command (with -l option) to get a copy of the crontab

To notify cron that there is a new crontab file U don't need a temporary file:
	crontab -l |  <script>  | crontab
where  <script>  will usually be a sed(1) script.