Timezone EDT -> EST issue with 13.37?
Either KDE or Slackware failed to fall back an hour this morning.
Dump of /etc/localtime: Code:
/etc/localtime Sun Nov 6 05:59:59 2011 UTC = Sun Nov 6 01:59:59 2011 EDT isds Code:
# date The time didn't fall back one hour. That's interesting. I executed tzselect and received the following results for TZ='America/Detroit' Code:
The following information has been given: Slackware 13.37 64bit ntp is not setup. KDE version - whatever is shipped with Slackware 13.37 |
Hi,
EDIT: sorry, did not see you did what was below, does Mich use a different time that NY, what is below is for NY: Worked for me :) Give this a try, it will tell you about your default timezone settings: /usr/sbin/zdump -v /etc/localtime | grep 2011 for EST/EDT I get, and if it does not match what you get maybe you have a old timezone db /etc/localtime Sun Mar 13 06:59:59 2011 UTC = Sun Mar 13 01:59:59 2011 EST isdst=0 gmtoff=-18000 /etc/localtime Sun Mar 13 07:00:00 2011 UTC = Sun Mar 13 03:00:00 2011 EDT isdst=1 gmtoff=-14400 /etc/localtime Sun Nov 6 05:59:59 2011 UTC = Sun Nov 6 01:59:59 2011 EDT isdst=1 gmtoff=-14400 /etc/localtime Sun Nov 6 06:00:00 2011 UTC = Sun Nov 6 01:00:00 2011 EST isdst=0 gmtoff=-18000 Jack |
I'm in Ontario and use EST5EDT as my timezone when setting machines up. Fallback happened as expected this morning.
|
Quote:
Hope this helps some. |
What glibc-zoneinfo package do you have installed?
Mine (which worked correctly) is glibc-zoneinfo-2.13-noarch-4 |
Set the Hardware Clock to the current System Time:
# hwclock --systohc |
Quote:
|
Quote:
Not so. when I run tzselect I have the two Michigan options: Code:
2) Eastern Time - Michigan - most locations BTW: I manually fixed it by using the "date -s" command. I'll have to see if it moves forward next spring. |
Quote:
|
I go through this every 6 months or so. I google, I search linuxquestions, I listen to my wife say "It works fine on Windows", then I set the time manually and promise myself to solve it, and then forget.
Running 3 Slackware, home workstation (13.37, 64-bit), laptop (current, 32), and an always-on crufty old PIII (current, 32). Only the PIII has the correct time right now. So I have a theory: having the hardware clock set to local time (the default) means that you have to have the machine running during the time-change to work correctly. My workstation and laptop were off last night. Right? Wrong? Should I just switch to UTC hw clock to solve this? |
Quote:
|
got this here glibc-zoneinfo-2.13_multilib-noarch-4alien and the laptop was in "suspend to ram" and it came up fine with the correct time on Sunday
|
Quote:
I don't mind setting the correct time twice a year, but this is the 21st century after all. |
Couldn't this issue be resolved by running /etc/rd.d/rc.ntpd, as mentioned in T3slider's post?
Doesn't windows automagically update its time settings because there's a time server running? cheers, |
Quote:
|
All times are GMT -5. The time now is 04:46 PM. |