From owner-freebsd-questions Tue Apr 4 11:21:54 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA18591 for questions-outgoing; Tue, 4 Apr 1995 11:21:54 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA18582 for ; Tue, 4 Apr 1995 11:21:52 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA15283; Tue, 4 Apr 95 12:10:19 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9504041810.AA15283@cs.weber.edu> Subject: Re: cron skipped jobs during ST->DST change To: pritc003@maroon.tc.umn.edu (Mike Pritchard) Date: Tue, 4 Apr 95 12:10:19 MDT Cc: paul@isl.cf.ac.uk, ghelmer@alpha.dsu.edu, freebsd-questions@FreeBSD.org In-Reply-To: <199504040728.CAA07834@mpp.com> from "Mike Pritchard" at Apr 4, 95 02:28:45 am X-Mailer: ELM [version 2.4dev PL52] Sender: questions-owner@FreeBSD.org Precedence: bulk > I've used systems in the past that got this all right. During either > time change, every scheduled cron job was run once and only once as long > as cron remained running during that magic hour. Yes; this is a bug in cron. The problem with firing all the jobs in the time period is sequence dependencies. You can argue that timing should not be used for most sequences ; thats is, dependent operations should all be fired by the same shell script. The problem with this ideal is that the sequence could be defined such that a backup will fire when the machine is assumed to be relatively idle. People who live in DST areas and fire backups at 2AM exactly should get their heads examined anyway. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.