From owner-freebsd-hackers Tue Apr 7 03:30:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA03218 for freebsd-hackers-outgoing; Tue, 7 Apr 1998 03:30:56 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA03200 for ; Tue, 7 Apr 1998 03:30:53 -0700 (PDT) (envelope-from dec@phoenix.its.rpi.edu) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.8/8.8.7) with SMTP id GAA04515; Tue, 7 Apr 1998 06:30:46 -0400 (EDT) (envelope-from dec@phoenix.its.rpi.edu) Date: Tue, 7 Apr 1998 06:30:46 -0400 (EDT) From: "David E. Cross" To: Studded cc: "James E. Housley" , hackers@FreeBSD.ORG Subject: Re: Daylight Savings Time - bug In-Reply-To: <3529F3FD.EA4D2619@san.rr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Apr 1998, Studded wrote: > James E. Housley wrote: > 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. :) I personally like the idea of having cron scripts run based on UTC... no need to worry about DST, just the occasionaly leap second to throw you off ;) -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message