Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ames!ncar!gatech!hubcap!ncrcae!ncrlnk!ciss!tmoore
From: tmoore@ciss.Dayton.NCR.COM (Tom.Moore@ciss.Dayton.NCR.COM)
Newsgroups: comp.bugs.sys5
Subject: Re: Crontab
Keywords: crontab bugs ncr
Message-ID: <808@ciss.Dayton.NCR.COM>
Date: 24 Jul 89 12:26:03 GMT
References: <138@tcnz2.tcnz.co.nz> <139@tcnz2.tcnz.co.nz>
Organization: NCR Corp. Network Application Services
Lines: 26

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).

To quote the TOWER User Reference Manual crontab(1) entry:

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

I don't believe copy implies append.

If it is any consolation, you are not the first person to make this
mistake. :-)

-- 
* Tom Moore                NCR Corporation  PCD-6              (513) 445-1373 *
* Consulting Analyst       1700 S. Patterson Blvd.         VOICEplus 622-1373 *
* Network Applications     Dayton, OH 45479          Tom.Moore@Dayton.NCR.COM *