handle timing normally except when clock jumps between 1 and 3 hours. If it

jumps, attempt as best as possible to gaurantee that jobs DO run, but only
run ONCE; patch by thompson@.tgsoft.com

1 files changed, 16 insertions, 1 deletions

diff --git a/usr.sbin/cron/cron.8 b/usr.sbin/cron/cron.8
index 8270b457d9d..a76c2efa313 100644
--- a/usr.sbin/cron/cron.8
+++ b/usr.sbin/cron/cron.8
@@ -15,7 +15,7 @@
 .\" * Paul Vixie          <paul@vix.com>          uunet!decwrl!vixie!paul
 .\" */
 .\" 
-.\" $Id: cron.8,v 1.1 1995/10/18 08:47:30 deraadt Exp $
+.\" $Id: cron.8,v 1.2 1997/12/22 08:10:40 deraadt Exp $
 .\" 
 .TH CRON 8 "20 December 1993"
 .UC 4
@@ -54,6 +54,21 @@ need not be restarted whenever a crontab file is modified.  Note that the
 .IR Crontab (1)
 command updates the modtime of the spool directory whenever it changes a
 crontab.
+.PP
+Special considerations exist when the clock is changed by less than 3
+hours, for example at the beginning and end of daylight savings
+time. If the time has moved forwards, those jobs which would have
+run in the time that was skipped will be run soon after the change. 
+Conversely, if the time has moved backwards by less than 3 hours,
+those jobs that fall into the repeated time will not be run.
+.PP
+Only jobs that run at a particular time (not specified as
+@hourly, nor with '*' in the hour or minute specifier) are
+affected. Jobs which are specified with wildcards are run based on the
+new time immediately.
+.PP
+Clock changes of more than 3 hours are considered to be corrections to
+the clock, and the new time is used immediately.
 .SH "SEE ALSO"
 crontab(1), crontab(5)
 .SH AUTHOR