Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!hubcap!ncrcae!wescott
From: wescott@ncrcae.Columbia.NCR.COM (Mike Wescott)
Newsgroups: comp.bugs.sys5
Subject: Re: Crontab
Keywords: crontab bugs ncr
Message-ID: <4781@ncrcae.Columbia.NCR.COM>
Date: 24 Jul 89 12:29:42 GMT
References: <138@tcnz2.tcnz.co.nz> <139@tcnz2.tcnz.co.nz> <2271@auspex.auspex.com>
Reply-To: wescott@ncrcae.Columbia.NCR.COM (Mike Wescott)
Organization: NCR Corp., Engineering & Manufacturing - Columbia, SC
Lines: 30

In article <2271@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes:
> In article <139@tcnz2.tcnz.co.nz> greg@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.
> 
> Unless somebody at NCR decided to modify "crontab" but didn't get it
> right,

Nope.  No modifications. Except expanding the usage message to include the
-l option.

> it's the manual that's incorrect;
	[...]
> I suspect, though, that it's purely a documentation screwup.

Nope.  The man page for crontab, while not a verbatim copy of the V.2.1
man page uses the same language:

	Crontab copies the specified file, or standard input if no
	file is specified, into a directory that holds all user
	crontab files.

This isn't the clearest and most complete description of crontab's behavior
but I don't see the "append" implication either.
-- 
	-Mike Wescott
	 mike.wescott@ncrcae.Columbia.NCR.COM