🚀 go-pugleaf

In <gfqx9!-@rpi.edu> gad@eclipse.its.rpi.edu (Garance A. Drosehn) writes:

>I'd like a better cron too.
> 
>> [..] Each user is able to create, list, and edit his/her  
>> own crontab. 

Maybe this should be edited into an FAQ-answer.  

1.  Next's cron is standard BSD.  It works.  Better would be nice, 
but there's no reason for abusive talk about it.  

2.  Paul Vixie (who is, I think, moderator of one of the 
comp.sources newsgroups) has a cron system that he wrote that 
provides individual user crontabs.  It is freely available, is 
better than the SysV cron system (except that it doesn't include 
"at", so you'll have to keep using Next's vanilla BSD "at" that 
depends on cron), and has worked perfectly here (on 12 machines) 
for months.  I don't like a couple of Paul's design decisions, but
haven't considered them important enough to waste time changing.

3.  I think Paul can be reached as paul@vixie.sf.ca.us; he also has 
one or more addresses at Dec, I believe.  

4.  This pachage should be at the archive sites, but isn't.  I will 
be happy to NextMail my copy to one person with ftp access (I don't 
have it) who promises to upload it to the various Next archive 
sites, including Purdue for sure.  

I can include binaries along with the source, for those who need 
them.  But since the cron daemon runs as root, even if you cannot 
compile code and want to trust me, you owe it to yourself to peruse 
the source code, in case I wasn't careful enough myself and missed 
something.  Thus, I don't want to supply just binaries.
-- 
 Irving_Wolfe@Happy-Man.com      Happy Man Corp. 206/463-9399 x101
 4410 SW Pt. Robinson Rd., Vashon Island, WA  98070-7399  fax x108
 We publish SOLID VALUE for the intelligent investor.  NextMail OK
Info free; sample $20: Send POSTAL addr: Solid-Value@Happy-Man.com