🚀 go-pugleaf

In article <1992Jul18.172701.3216@fishbone.uucp>  
grace!fishbone!jdyer@moscom.com (John D. Dyer) writes:
> Perhaps I'm expecting too much, but I'm very disappointed with the way  
> NeXT has implemented cron.  On the NeXT, if cron has been started, only  
> the /etc/crontab, /etc/crontab.local files are checked.  These files are  
> accessible only by the SA of the machine.  On a SUN SPARCStation, the SA  
> has the ability to add trusted users to a filename to enable them to run  
> their own cron jobs.  Each user is able to create, list, and edit  
his/her  
> own crontab.  Is NeXT's implementation NeXT specific, or does it go  
deeper  
> than that to mach or bsd?  Any help would be appreciated.  Thanks in  
> advance.
> 

I agree!  Are you listening NeXT!!!  This cron is old and feeble. I'm a
hardy NeXT advocate, but the Sun's have had this capability for the
past few releases. You can create your own crontab, and install it by
typing "crontab filename". This places "filename" in your
/usr/spool/cron/crontabs directory, and places it under the
domain of the cron daemon.

Sure, there are a lot of workarounds, but I'm not buying.  I'm
using state of the art machinery, and I expect the software to
follow suit.  Let's get with the times...
--
---------------------------------------------------------------------
| Brad Skrbec       | "For it is the doom of men that they forget." |
| Motorola Cellular     |                         -- Merlin         |
| Arlington Heights, IL | Internet: skrbec@rtsg.mot.com             |
|                       | Home: brad@darby.chi.il.us                |
------------------------------- NeXTMail Gladly Accepted ------------