Date: Fri, 19 Jan 2007 11:36:05 +1100 From: "Murray Taylor" <MTaylor@bytecraft.com.au> To: <jgrosch@juniper.net>, "hal" <hal@cc.usu.edu> Cc: freebsd-questions@freebsd.org Subject: RE: Daylight savings time / 6.1 and 4.11 Message-ID: <04E232FDCD9FBE43857F7066CAD3C0F126733C@svmailmel.bytecraft.internal>
next in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-questions@freebsd.org=20 > [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Josef Grosch > Sent: Friday, 19 January 2007 10:59 AM > To: hal > Cc: freebsd-questions@freebsd.org > Subject: Re: Daylight savings time / 6.1 and 4.11 >=20 > On Tue, Jan 16, 2007 at 01:31:22PM -0700, hal wrote: > > This came down from above?! > >=20 > > Beginning in 2007, Daylight Savings Time will be lengthened=20 > one month =20 > > by starting three weeks earlier (2AM on the second Sunday=20 > in March) =20 > > and ending one week later (2AM on the first Sunday in November). > >=20 > >=20 > > What patch levels do I need to be at for my 4.7 and 6.1=20 > systems to be > > daylight savings 2007 ready? > >=20 > > Currently: 4.11-RELEASE-p25 > >=20 > > Currently: 6.1-RELEASE-p10 > >=20 > > hal >=20 >=20 > This is an issue here at work. We have very many FreeBSD 4.x=20 > machines and a > growing number of FreeBSD 6.x. The change when daylight=20 > saving time starts > and ends is an issue for machines in the United States and, we think, > those in Canada. The way to check if your zone file is=20 > correct is to do >=20 > zdump -v /etc/localtime | more >=20 > Look for the following >=20 >=20 > /etc/localtime Sun Mar 11 09:59:59 2007 UTC =3D Sun Mar 11=20 > 01:59:59 2007 PST isdst=3D0 gmtoff=3D-28800 > /etc/localtime Sun Mar 11 10:00:00 2007 UTC =3D Sun Mar 11=20 > 03:00:00 2007 PDT isdst=3D1 gmtoff=3D-25200 > /etc/localtime Sun Nov 4 08:59:59 2007 UTC =3D Sun Nov 4=20 > 01:59:59 2007 PDT isdst=3D1 gmtoff=3D-25200 > /etc/localtime Sun Nov 4 09:00:00 2007 UTC =3D Sun Nov 4=20 > 01:00:00 2007 PST isdst=3D0 gmtoff=3D-28800 >=20 > If you see this, your zone file will handle the change=20 > correctly. The 6.x > series has the corrected zone files. 4.x does not have this.=20 > The best way > to handle this is to copy the zone file from=20 > /usr/share/zoneinfo on a 6.x > machine to your 4.x.=20 >=20 >=20 > Josef > port misc/zoneinfo runs on all os versions, fixes all zone files=20 caveat: current ports tree caveat: only works if the DST change has been added to the NIST=20 =20 master files ....=20 mjt --------------------------------------------------------------- The information transmitted in this e-mail is for the exclusive use of the intended addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material.=20 E-mails may not be secure, may contain computer viruses and may be corrupted in transmission. Please carefully check this e-mail (and any attachment) accordingly. No warranties are given and no liability is accepted for any loss or damage caused by such matters. --------------------------------------------------------------- ### This e-mail message has been scanned for Viruses by Bytecraft ###
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?04E232FDCD9FBE43857F7066CAD3C0F126733C>