home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!decwrl!concert!duke!khera
- From: khera@cs.duke.edu (Vivek Khera)
- Newsgroups: comp.sys.next.sysadmin
- Subject: Re: Is cron going to get better?
- Message-ID: <KHERA.92Jul21101158@thneed.cs.duke.edu>
- Date: 21 Jul 92 14:11:58 GMT
- References: <1992Jul18.172701.3216@fishbone.uucp> <1992Jul20.221450.15442@cs.sfu.ca>
- Sender: news@duke.cs.duke.edu
- Organization: Duke University CS Dept., Durham, NC
- Lines: 28
- Nntp-Posting-Host: thneed.cs.duke.edu
- In-reply-to: oneill@cs.sfu.ca's message of 20 Jul 92 22:14:50 GMT
- X-Md4-Signature: 3cabf027795c513dde2cfe43309daa5d
-
- In article <1992Jul20.221450.15442@cs.sfu.ca> oneill@cs.sfu.ca (Richard O'Neill) writes:
-
- I belive that NeXT implemented the standard BSD4.3 cron program, so either
- Sun chose to be different, or it is a SysVism that they've adopted.
- Personally I have always believed that they re-wrote all the cron type code
- because the 'at' command didn't work in SunOS 3.5.
-
- Sun adopted System V cron for SunOS 4. the idea is good, but the
- implementation leaves much to be desired. there are problems with
- cron not "doing the right thing" at the change to/from daylight
- savings time. there are also reports of cron executing some jobs
- multiple times. it also executes your cron jobs with a shell that
- thinks it is interactive; this causes no end of confusion for people
- who have always had something like this in their .cshrc:
-
- if (! $?prompt ) then
- exit
- endif
-
- to differentiate between interactive and non-interactive shell executions.
-
- there are other cron implementations out there. i believe that
- someone mentioned Paul Vixie's as a viable alternative.
- --
- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
- Vivek Khera, Gradual Student/Systems Guy Department of Computer Science
- Internet: khera@cs.duke.edu Duke University
- (MIME mail accepted) Durham, NC 27706 (919) 660-6528
-