Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!umigw!ibiza!aem
From: aem@ibiza.cs.miami.edu (a.e.mossberg)
Newsgroups: comp.bugs.sys5
Subject: Re: Crontab
Keywords: crontab bugs ncr
Message-ID: <484@umigw.MIAMI.EDU>
Date: 21 Jul 89 18:17:21 GMT
References: <138@tcnz2.tcnz.co.nz> <139@tcnz2.tcnz.co.nz>
Sender: news@umigw.MIAMI.EDU
Reply-To: aem@Mthvax.CS.Miami.Edu
Lines: 27

greg@tcnz2.tcnz.co.nz writes:
>In NCR Tower Unix, release 20100, if I create a crontab format file as
>root then do
>crontab filename
>it wipes what is currently in the crontab for root and replaces it with
>the new entries. It does not append it, as the manual implies. We didn't
>have cron.allow or cron.deny set up, so root was the only one able
>to use cron (all the users are naive users).
>This means I must manually reload the thing myself

That's exactly how System V crontab works and is supposed to work, as far
as I can tell. It works that way on our ATT 3B2s, and our Apple Mac A/UX
systems.

When I don't feel like vi-ing the appropriate file, I do crontab >tempfile,
vi tempfile,
crontab tempfile


aem



a.e.mossberg - aem@mthvax.cs.miami.edu/aem@umiami.BITNET - Pahayokee Bioregion
The life of money-making is one undertaken under compulsion, and wealth is 
evidently not the good we are seeking, for it is merely useful for the sake 
of something else.					- Aristotle