Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.unix.questions
Subject: Re: Periodic execution of a program
Message-ID: <5605@auspex.auspex.com>
Date: 30 Jan 91 19:23:30 GMT
References: <5830@rex.cs.tulane.edu> <1991Jan28.153105.2996@mcs.drexel.edu> <3327@unisoft.UUCP>
Organization: Auspex Systems, Santa Clara
Lines: 17


 >Just about every man page I've seen for the at command has the following
 >in it:
 >
 >   BUGS
 >        Due to the granularity of the execution of /usr/lib/atrun,
 >        there may be bugs in scheduling things almost exactly 24
 >        hours into the future.
 >   
 >This includes SunOS, Pyramid, Vax, and a number of others.  You 
 >may run into this problem.

It's missing from the AT(1) man page on the SunOS 4.0.3 machine on which
I'm typing this.  Part of the reason for that is that SunOS 4.x uses the
S5 "cron"/"at" package, which doesn't *HAVE* "/usr/lib/atrun"; instead,
"cron" runs both "cron" and "at" jobs, rather than "/usr/lib/atrun"
being run every 15 minutes or whatever out of "crontab".