Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!ucsd!ucsdhub!hp-sdd!ncr-sd!ncrcae!sauron!wescott
From: wescott@sauron.Columbia.NCR.COM (Mike Wescott)
Newsgroups: comp.unix.questions
Subject: Re: Cron
Message-ID: <1012@sauron.Columbia.NCR.COM>
Date: 30 Jan 88 20:49:30 GMT
References: <235014@<1988Jan17> <10800014@bradley> <940@nesac2.UUCP>
Reply-To: wescott@sauron.Columbia.NCR.COM (Mike Wescott)
Organization: Entry Level Systems Development, NCR Corp., Columbia, SC
Lines: 22

> Was I the only recipient of the information that you can get cron to
> accept new data in a particular crontab file by:
> 1) cd /usr/spool/cron/crontabs
> 1a) cp root root.bk  (skip this if you never make mistakes :-)
> 2) ed root
> 3) make changes, write, quit
> 4) crontab root
> 5) cd back_to_where_you_started

No. Don't do that.  Use the "crontab -l" to get a copy
to edit:

1) crontab -l > Crontab
2) ed Crontab
3) make changes, write, quit
4) crontab Crontab

Much safer.  Works for anybody that has permission to use cron.
You don't need to be superabuser to use.  Crontabs are usually 
-r--r--r-- and owned by root.
-- 
	-Mike Wescott
	 wescott@ncrcae.Columbia.NCR.COM