From owner-freebsd-hackers Tue Apr 7 02:39:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26102 for freebsd-hackers-outgoing; Tue, 7 Apr 1998 02:39:24 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt050n33.san.rr.com [204.210.31.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26097 for ; Tue, 7 Apr 1998 02:39:22 -0700 (PDT) (envelope-from Studded@san.rr.com) Received: from san.rr.com (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id CAA07594; Tue, 7 Apr 1998 02:38:05 -0700 (PDT) (envelope-from Studded@san.rr.com) Message-ID: <3529F3FD.EA4D2619@san.rr.com> Date: Tue, 07 Apr 1998 02:38:05 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE-0325 i386) MIME-Version: 1.0 To: "James E. Housley" CC: hackers@FreeBSD.ORG Subject: Re: Daylight Savings Time - bug References: <3528F1B4.7BE87776@pr-comm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG James E. Housley wrote: > > Did anyone else notice that the Sunday AM Daily and Security scripts > didn't run with the change of time to daylight savings? Is this a know > glitcht that only happens once a year and there for is not a big > problem? Before I forget, your .sig is way too long. Some would say that the traditional 4 lines is also too long, but most of the info in yours is better suited in a finger somewhere. That said, this is a known problem. I suggested a band-aid solution a while back, namely setting the daily script to run at 1:59 am. That would eliminate the problem for the vast majority of the western world minus a few european countries that do the change from 1 to 2 am or 1:30 to 2:30. At the time I was told that because there is no time to run the job that completely eliminates the possibility of conflict, no change would be made. Personally I think that kind of reasoning is nuts, but I don't get to make decisions around here. :) As others have already indicated, the simplest solution at this point is to reschedule the job locally. Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message