Path: utzoo!utgpu!water!watmath!clyde!burl!codas!ablnc!maxwell
From: maxwell@ablnc.ATT.COM (Robert Maxwell)
Newsgroups: comp.unix.questions
Subject: Re: Cron
Summary: Sometimes you can't read your own crontab
Message-ID: <452@ablnc.ATT.COM>
Date: 1 Feb 88 14:53:23 GMT
References: <235014@<1988Jan17> <10800014@bradley> <940@nesac2.UUCP> <1012@sauron.Columbia.NCR.COM>
Organization: AT&T, Maitland, Florida
Lines: 26

In article <1012@sauron.Columbia.NCR.COM>, wescott@sauron.Columbia.NCR.COM (Mike Wescott) writes:
> 
> No. Don't do that.  Use the "crontab -l" to get a copy
> to edit:
...
> 
> 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.
> -- 
If you are paranoid and use a 077 umask setting, your own crontab file
will be -r-------- and owned by root. The crontab -l is the only way
you can even read your crontab file.

I think it has been mentioned, but using the crontab command to insert
the new crontab file causes cron to scan the file and reschedule the
jobs.




-- 
-----------------------------------------------------------------------------
Bob Maxwell	AT&T DP&CT	     |	All standard (and most non_standard)
Maitland, FL	ihnp4!ablnc!maxwell  |  disclaimers apply.
-----------------------------------------------------------------------------