I read a few days back on the list where the tzdata rpm was to take care of the new DST rules. I run CentOS 3 servers, and did a 'yum update tzdata' , but received a 2006a update of the rpm. Is this proper? It sure didn't fix anything. Thanks Steve Campbell campbell at cnpapers.com Charleston Newspapers
Steve Campbell wrote:> I read a few days back on the list where the tzdata rpm was to take > care of the new DST rules. I run CentOS 3 servers, and did a 'yum > update tzdata' , but received a 2006a update of the rpm. > > Is this proper? It sure didn't fix anything. > > Thanks > > Steve CampbellYou can use the "zdump" to verify the DST rules. Substitute the right timezone in the command below: $ /usr/sbin/zdump -v "US/Pacific" -c 2006,2008 US/Pacific Fri Dec 13 20:45:52 1901 UTC = Fri Dec 13 12:45:52 1901 PST isdst=0 gmtoff=-28800 US/Pacific Sat Dec 14 20:45:52 1901 UTC = Sat Dec 14 12:45:52 1901 PST isdst=0 gmtoff=-28800 US/Pacific Sun Apr 2 09:59:59 2006 UTC = Sun Apr 2 01:59:59 2006 PST isdst=0 gmtoff=-28800 US/Pacific Sun Apr 2 10:00:00 2006 UTC = Sun Apr 2 03:00:00 2006 PDT isdst=1 gmtoff=-25200 US/Pacific Sun Oct 29 08:59:59 2006 UTC = Sun Oct 29 01:59:59 2006 PDT isdst=1 gmtoff=-25200 US/Pacific Sun Oct 29 09:00:00 2006 UTC = Sun Oct 29 01:00:00 2006 PST isdst=0 gmtoff=-28800 US/Pacific Sun Mar 11 09:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 PST isdst=0 gmtoff=-28800 US/Pacific Sun Mar 11 10:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 PDT isdst=1 gmtoff=-25200 US/Pacific Sun Nov 4 08:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 PDT isdst=1 gmtoff=-25200 US/Pacific Sun Nov 4 09:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 PST isdst=0 gmtoff=-28800 US/Pacific Mon Jan 18 03:14:07 2038 UTC = Sun Jan 17 19:14:07 2038 PST isdst=0 gmtoff=-28800 US/Pacific Tue Jan 19 03:14:07 2038 UTC = Mon Jan 18 19:14:07 2038 PST isdst=0 gmtoff=-28800 You can see DST takes effect on March 11 this year, so the rules are updated. This output was from a CentOS 4 system, but I'd imagine the results should be the same on CentOS 3. -Greg
On 2/7/07, Steve Campbell <campbell at cnpapers.com> wrote:> I read a few days back on the list where the tzdata rpm was to take care of > the new DST rules. I run CentOS 3 servers, and did a 'yum update tzdata' , > but received a 2006a update of the rpm. > > Is this proper? It sure didn't fix anything. > > Thanks > > Steve Campbell > campbell at cnpapers.com > Charleston Newspapers > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >So what happens when you run this command to confirm the fix? zdump -v CST6CDT | grep 2007 According this link at IBMs support docs you should see something like.. On a system with the adjustments you will see: CST6CDT Sun Mar 11 07:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 CST isdst=0 gmtoff=-21600 CST6CDT Sun Mar 11 08:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 CST isdst=0 gmtoff=-18600 CST6CDT Sun Nov 4 06:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 CST isdst=0 gmtoff=-18600 CST6CDT Sun Nov 4 07:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 CST isdst=0 gmtoff=-21600 Here is the IBM link. Sorry its not tiny'd http://www-1.ibm.com/support/docview.wss?rs=0&q1=T1010301&uid=isg3T1010301&loc=en_US&cs=utf-8&cc=us&lang=en --Rickp
Steve Campbell wrote:> I read a few days back on the list where the tzdata rpm was to take care of > the new DST rules. I run CentOS 3 servers, and did a 'yum update tzdata' , > but received a 2006a update of the rpm.You did get that from the fasttrack repository, as I wrote in that thread? [admin at mail-gw-2 admin]$ rpm -q tzdata tzdata-2006m-3.el3 Regards, Ralph -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20070207/9be8315b/attachment.sig>