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@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 Campbell
You 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
Greg Bailey wrote:
You 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.
On a side note, but kind of on-topic, I want to set my box to live in a different timezone. In my case, I actually want the box to live in GMT +0000, how would I go about doing that? I have this sneaky suspicion it's a sneaky little file somewhere, but I haven't been able to locate it.
Peter
Peter Serwe wrote:
On a side note, but kind of on-topic, I want to set my box to live in a different timezone. In my case, I actually want the box to live in GMT +0000, how would I go about doing that? I have this sneaky suspicion it's a sneaky little file somewhere, but I haven't been able to locate it.
As much as I love answering my own posts,
# zic -l GMT
worked admirably for changing my timezone.
Peter
Peter Serwe wrote:
Greg Bailey wrote:
You 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.
On a side note, but kind of on-topic, I want to set my box to live in a different timezone. In my case, I actually want the box to live in GMT +0000, how would I go about doing that? I have this sneaky suspicion it's a sneaky little file somewhere, but I haven't been able to locate it.
cp the correct /usr/share/zoneinfo file to /etc/localdata, and also update /etc/sysconfig/(I forget) to have the TZ=therightthing.
John R Pierce wrote:
cp the correct /usr/share/zoneinfo file to /etc/localdata, and also update /etc/sysconfig/(I forget) to have the TZ=therightthing.
Hilariously, zic -l GMT does nothing more than make a symbolic link..
1 lrwxrwxrwx 1 root root 26 Feb 8 23:51 localtime -> ..//usr/share/zoneinfo/GMT
"El-oh-Elll"
:)
Peter
Peter Serwe wrote:
John R Pierce wrote:
cp the correct /usr/share/zoneinfo file to /etc/localdata, and also update /etc/sysconfig/(I forget) to have the TZ=therightthing.
Hilariously, zic -l GMT does nothing more than make a symbolic link..
1 lrwxrwxrwx 1 root root 26 Feb 8 23:51 localtime -> ..//usr/share/zoneinfo/GMT
mmmm. on the glibc mail list archives I saw posts where they VERY specifically -stopped- sym linking a number of versions back... rationale was that if /usr or /usr/share is on a different filesystem than /etc, you will have problems with your log timestamps during bootup and in single user.
John R Pierce wrote:
mmmm. on the glibc mail list archives I saw posts where they VERY specifically -stopped- sym linking a number of versions back... rationale was that if /usr or /usr/share is on a different filesystem than /etc, you will have problems with your log timestamps during bootup and in single user.
Bah ... who needs log timestamps on bootup?
:P
Thanks much, I'll change that out with a 'cp'.
Peter
Peter Serwe wrote:
John R Pierce wrote:
mmmm. on the glibc mail list archives I saw posts where they VERY specifically -stopped- sym linking a number of versions back... rationale was that if /usr or /usr/share is on a different filesystem than /etc, you will have problems with your log timestamps during bootup and in single user.
Bah ... who needs log timestamps on bootup?
:P
Thanks much, I'll change that out with a 'cp'.
Ne sure to remove the symlink first:->>
On 2/7/07, Steve Campbell campbell@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@cnpapers.com Charleston Newspapers
CentOS mailing list CentOS@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=isg3T1...
--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@mail-gw-2 admin]$ rpm -q tzdata tzdata-2006m-3.el3
Regards,
Ralph
-
Greg Bailey -
John R Pierce -
John Summerfield -
Peter Serwe -
Ralph Angenendt -
Rick Philbrick -
Steve Campbell