Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!rutgers!pyrnj!pdk
From: pdk@pyrnj.uucp (Paul Kramer)
Newsgroups: comp.sys.pyramid
Subject: Re: Mailing the output of a command run from cron
Message-ID: <14894@pyrnj.uucp>
Date: 16 Apr 91 15:15:19 GMT
References: <1031@lucifer.UUCP> <1991Apr15.215936.27605@newross.Princeton.EDU>
Reply-To: pdk@pyrnj.UUCP (Paul Kramer)
Organization: Pyramid Technology Corp, Woodbridge, NJ
Lines: 17

In article <1991Apr15.215936.27605@newross.Princeton.EDU> tr@samadams.princeton.edu (Tom Reingold) writes:
>If you use the cron in the att universe, you will get this
>automatically.  Not only that, ordinary users can use cron in the att
>universe.  They must (and the superuser ought to) use the "crontab"
>command for updating their personal crontab files.

FYI:

If the super user places an entry in the 'cron.allow' file for
that user, they should be allowed to update entries in their
own crontab file with impunity using the crontab(1) command.
If this file does not exist, then they may still be allowed
to use the crontab(1) command if their id does not appear in
the 'cron.deny' file.

cheers,
paul davis kramer