From owner-freebsd-questions@FreeBSD.ORG Mon Mar 11 12:49:48 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 65129D32 for ; Mon, 11 Mar 2013 12:49:48 +0000 (UTC) (envelope-from fbsd8@a1poweruser.com) Received: from mail-03.name-services.com (mail-03.name-services.com [69.64.155.195]) by mx1.freebsd.org (Postfix) with ESMTP id 3B9E9ED4 for ; Mon, 11 Mar 2013 12:49:47 +0000 (UTC) Received: from [10.0.10.1] ([173.88.202.176]) by mail-03.name-services.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 11 Mar 2013 05:49:49 -0700 Message-ID: <513DD2E9.2040700@a1poweruser.com> Date: Mon, 11 Mar 2013 08:49:45 -0400 From: Fbsd8 User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Ben Cottrell Subject: Re: day light saving time happened today References: <513CC4C4.8080405@a1poweruser.com> <513D0026.6030109@a1poweruser.com> <5C91A731-BF1E-4FD2-AB26-5348F0685967@wolfhut.org> <513D0FBA.1070303@a1poweruser.com> <44fw02lt0d.fsf@lowell-desk.lan> <513D369C.8080907@a1poweruser.com> <20130310215632.3c0344f2@europa> <513D3EEB.3020201@a1poweruser.com> <57B1D1B8-5DBC-41C9-AB76-55687AB45359@wolfhut.org> In-Reply-To: <57B1D1B8-5DBC-41C9-AB76-55687AB45359@wolfhut.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 11 Mar 2013 12:49:49.0235 (UTC) FILETIME=[EA9AB030:01CE1E56] X-Sender: fbsd8@a1poweruser.com X-Authenticated-Sender: fbsd8@a1poweruser.com X-EchoSenderHash: [fbsd8]-[a1poweruser*com] Cc: Mike Jeays , freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 12:49:48 -0000 Ben Cottrell wrote: > On Mar 10, 2013, at 19:18, Fbsd8 wrote: >> What is really needed is for the tzsetup program to state which east coast selections have day light saving included. Maybe a pr is in order. > > Nope, you pretty conclusively proved that you're using the right > time zone setting. Trust me. :-) That md5 you posted is the exact > same md5 that's on my own system. My own America/New_York is > doing just fine, thank you. ;-) > > Something else is going on. *What*, I don't know. But you chose > the right time zone in tzsetup and that time zone description > file definitely does have DST rules in it. > > I never use the wall_cmos_clock setting, because I don't trust > it -- at least with the traditional behavior (wall_cmos_clock=0) > I know *exactly* what's going on. I really don't know what is > happening under the hood when that's turned on, so I have no > idea if it could be related or not. But I'm curious what > it shows if you run: > > sysctl machdep.wall_cmos_clock > > ~Ben > sysctl machdep.wall_cmos_clock returned 0 Ran this little test. Last night before turning off my system I used the date command to set the date to 3/9 with the correct DST. This morning when I turned on my system the time had advanced by one hour. So this proves that the time zone setting does have DST in it and every thing worked as expected. Even though the system is now on DST the date command still displays EDT. Does the date command ever show DST? Now about the question of why did the time not jump forward on the date it was suppose to? It all boils down to this, On 3/9 I did not check the time. I just expected it to be correct. Even though the date and time is displayed every morning when I boot my system, I have never in 20 years taken the time to verify if its correct on any of the many PCs I have used. It is totally possible that the system time was incorrect and I was just not aware of it before DST went into effect, after which I checked the time as I did with all the other clocks in the house. So for now, thats how I am leaving things.