Time didn't change (daylight savings)

Reasons · 2008-03-09 16:46:18

First off, I live in the Washington State in the United States. For some ungodly reason are daylight savings is different than everywhere else in the world, go figure. Anyways, this morning at 2 everything was supposed to go forward an hour but this computer didn't. I set it in my rc.conf, shouldn't that be it?

rc.conf

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="US/Pacific"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
#
# Modules to load at boot-up (in this order)
#   - prefix a module with a ! to blacklist it
#
MODULES=(iwl3945 !ipw3945 acpi-cpufreq !cpufreq_ondemand cpufreq_powersave sky2 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore !sony_pi sony_laptop !sony_acpi)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="reasons"
#
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available
# interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth0="dhcp"
wlan0="dhcp"
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(lo !eth0 !wlan0)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
#
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network-profiles
#
#NET_PROFILES=(main)

#
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(@syslog-ng @netfs @acpid @crond dbus @wicd @hal @alsa @fam @mpd gdm)

#SPLASH="fbsplash"

# End of file

dyscoria · 2008-03-09 16:52:58

I think you want UTC instead of localtime.

hmmm on second thoughts i think i'm wrong. UTC is just what I have set in mine.

Last edited by dyscoria (2008-03-09 16:54:47)

Reasons · 2008-03-09 17:19:59

Well after being confused a bit, even the BIOS didn't change which was probably it. Now to go figure out what happened.

Pudge · 2008-03-09 17:30:21

Last fall, the United States congress changed the date when Daylight Savings Time changed this spring. The U.S. changed last night, which is 3 weeks earlier than normal. I believe the rest of the world will not change for another 3 weeks. Once again the U.S. has to do something different than the rest of the world. My guess is that 3 weeks from now your computer will jump ahead an hour which is probably when the computer thinks this is supposed to take place.

Although I could be wrong.

Pudge

BC · 2008-03-09 17:34:59

Pudge wrote:

Last fall, the United States congress changed the date when Daylight Savings Time changed this spring. The U.S. changed last night, which is 3 weeks earlier than normal. I believe the rest of the world will not change for another 3 weeks. Once again the U.S. has to do something different than the rest of the world. My guess is that 3 weeks from now your computer will jump ahead an hour which is probably when the computer thinks this is supposed to take place.
Although I could be wrong.
Pudge

I don't think that's it (my time changed automatically). This was my setting:

HARDWARECLOCK="localtime"
TIMEZONE="America/New_York"

Pudge · 2008-03-09 17:41:52

In Gnome (I don't know anything about KDE) there is an option to either set the time manually, or to synchronize the time with an internet server. If your OS synchronizes to an internet server, that would have changed the time for you.

Pudge

Dusty · 2008-03-09 17:53:11

My time didn't change this morning either (Canada had to follow suit with the US or trade would have been too confusing.) I just ran ntpdate to update it. not sure if its going to change by itself in April or not...

Dusty

tesjo · 2008-03-09 18:12:35

My time was changed when I logged into XFCE, but I have to diiferent outputs here.

$ hwclock --show
Sun Mar  9 11:11:07 2008  -0.000214 seconds
$ date
Sun Mar  9 12:11:30 MDT 2008

date shows the correct DST as does XFCE. I dont know why this is, but maybe your clock program (you didn't say how you checked) is calling hwclock.

skymt · 2008-03-09 18:39:44

I know there was an update to the tzdata package on the 6th. Have those of you whose clocks didn't change gotten the update yet?

bgc1954 · 2008-03-09 20:34:40

You could also try this to keep your time up to date: http://wiki.archlinux.org/index.php/NTP

blu3ness · 2008-03-09 21:55:56

HARDWARECLOCK="UTC"

should od it?...

dyscoria · 2008-03-09 22:00:15

blu3ness wrote:

HARDWARECLOCK="UTC"
should od it?...

That's what I thought at first, but according to wikipedia:
"Local time is UTC plus the time zone offset for that location, plus an offset (typically +1) for daylight saving time, if in effect."

I've always thought UTC was the right one, but i've never actually had a chance to 'test' it as i've only used linux since November and no time changes have occurred yet

buttons · 2008-03-09 23:27:20

HARDWARECLOCK="localtime"
TIMEZONE="America/New_York"

Changed this morning as expected.

dmartins · 2008-03-10 00:18:45

UNIX type systems usually have their hardware clocks set to UTC then the offset based on your timezone is added along with an hour for DST if required. Windows likes your hardware clock set to your local time. If you dual boot you should use localtime and if you only run linux you can set it to UTC. I have always thought the timezone information provided by the tzdata package should take care of DST. However, my clock didn't change either.

Timezone is Canada/Eastern.
Clock set to localtime

Last edited by dmartins (2008-03-10 00:19:23)

iphitus · 2008-03-10 00:20:23

Rebooting ought to do it, the system will should set the time correctly when it sets the time at bootup.

You could do it by hand and extract the commands from rc.sysinit, but rebooting is easier.

Last edited by iphitus (2008-03-10 00:20:57)

ralvez · 2008-03-10 00:34:06

My time did update, however, I use NTP and that likely had an influence on the outcome.
My settings are:

HARDWARECLOCK="UTC"
TIMEZONE="Canada/Eastern"

p.s. Both my systems updated correctly

ep2011 · 2008-03-10 01:38:59

Happened to me as well.. I still can't fix it. I tried using both TIMEZONE="US/Eastern" and TIMEZONE="AMERICA/NEW_YORK" and both don't work.

edit: just tried using UTC instead of localtime for US/Eastern and it still doesn't work.. Help would really be appreciated. (Parents are snickering saying "what, linux doesn't change your clock?")

Last edited by ep2011 (2008-03-10 01:49:08)

ep2011 · 2008-03-10 20:02:17

I know i'm being impatient but can anyone help? This is really important... My clock is still wrong

tesjo · 2008-03-10 21:04:21

The issue seems to be with the tzdata updates and locale.gen. You should have an out put of zdump something like this

$ zdump -v US/Mountain | grep 2008
US/Mountain  Sun Mar  9 08:59:59 2008 UTC = Sun Mar  9 01:59:59 2008 MST isdst=0
US/Mountain  Sun Mar  9 09:00:00 2008 UTC = Sun Mar  9 03:00:00 2008 MDT isdst=1
US/Mountain  Sun Nov  2 07:59:59 2008 UTC = Sun Nov  2 01:59:59 2008 MDT isdst=1
US/Mountain  Sun Nov  2 08:00:00 2008 UTC = Sun Nov  2 01:00:00 2008 MST isdst=0

If you don't have the different on/offs for dst. Run locale-gen and check again. If still no check for /etc/locale.gen.pacnew

Now since it is past Mar 9, you may have to set time manually using the date command or something else, but come Nov it should switch off.

ep2011 · 2008-03-10 23:05:37

tesjo wrote:

The issue seems to be with the tzdata updates and locale.gen. You should have an out put of zdump something like this
$ zdump -v US/Mountain | grep 2008
US/Mountain  Sun Mar  9 08:59:59 2008 UTC = Sun Mar  9 01:59:59 2008 MST isdst=0
US/Mountain  Sun Mar  9 09:00:00 2008 UTC = Sun Mar  9 03:00:00 2008 MDT isdst=1
US/Mountain  Sun Nov  2 07:59:59 2008 UTC = Sun Nov  2 01:59:59 2008 MDT isdst=1
US/Mountain  Sun Nov  2 08:00:00 2008 UTC = Sun Nov  2 01:00:00 2008 MST isdst=0
If you don't have the different on/offs for dst. Run locale-gen and check again. If still no check for /etc/locale.gen.pacnew
Now since it is past Mar 9, you may have to set time manually using the date command or something else, but come Nov it should switch off.

My zdump command shows in the exact same format as you, with the same times and stuff (well not the same times, but the time difference between the 1st and 2nd, 2nd and 3rd, etc). My date command and hwclock both show an hour back. How should I fix it using the date command? Is there like a force time check thing other than rebooting? rebooting isn't working.

dmartins · 2008-03-10 23:14:19

date MMDDhhmm

date 03101913 would set the date to March 10th, 7:14

ep2011 · 2008-03-11 00:23:30

Thanks dmartins... That worked perfectly... I'll see if after a restart it doesnt reset itself, but hopefully it will stay like this

Last edited by ep2011 (2008-03-11 00:23:46)

bgc1954 · 2008-03-11 01:34:27

Yes, manually setting the time with date -s will work but next time daylight savings kicks in you will likely have the same problems. Using opennptd should correct the time according to network time protocol to keep your clock sync'd at all times. Works for me all the time with localtime and Canada/Mountian timezone. But setting your time manually also works so whatever floats your boat.

ep2011 · 2008-03-11 02:04:41

bgc1954 wrote:

Yes, manually setting the time with date -s will work but next time daylight savings kicks in you will likely have the same problems. Using opennptd should correct the time according to network time protocol to keep your clock sync'd at all times. Works for me all the time with localtime and Canada/Mountian timezone. But setting your time manually also works so whatever floats your boat.

Set up opennptd, and it works perfectly! I looked at the log and it adjusted my time .036 seconds lol... So I know it works

Reasons · 2008-03-11 03:26:02

Well I just noticed that during boot I now get this error though everything including the clock is fine.

/etc/rc.sysinit: line 302: [: too many arguments

the line in question
if [ "$TIMEZONE" != "" -a -e /usr/share/zoneinfo/$TIMEZONE ]; then

Arch Linux

#1 2008-03-09 16:46:18

Time didn't change (daylight savings)

#2 2008-03-09 16:52:58

Re: Time didn't change (daylight savings)

#3 2008-03-09 17:19:59

Re: Time didn't change (daylight savings)

#4 2008-03-09 17:30:21

Re: Time didn't change (daylight savings)

#5 2008-03-09 17:34:59

Re: Time didn't change (daylight savings)

#6 2008-03-09 17:41:52

Re: Time didn't change (daylight savings)

#7 2008-03-09 17:53:11

Re: Time didn't change (daylight savings)

#8 2008-03-09 18:12:35

Re: Time didn't change (daylight savings)

#9 2008-03-09 18:39:44

Re: Time didn't change (daylight savings)

#10 2008-03-09 20:34:40

Re: Time didn't change (daylight savings)

#11 2008-03-09 21:55:56

Re: Time didn't change (daylight savings)

#12 2008-03-09 22:00:15

Re: Time didn't change (daylight savings)

#13 2008-03-09 23:27:20

Re: Time didn't change (daylight savings)

#14 2008-03-10 00:18:45

Re: Time didn't change (daylight savings)

#15 2008-03-10 00:20:23

Re: Time didn't change (daylight savings)

#16 2008-03-10 00:34:06

Re: Time didn't change (daylight savings)

#17 2008-03-10 01:38:59

Re: Time didn't change (daylight savings)

#18 2008-03-10 20:02:17

Re: Time didn't change (daylight savings)

#19 2008-03-10 21:04:21

Re: Time didn't change (daylight savings)

#20 2008-03-10 23:05:37

Re: Time didn't change (daylight savings)

#21 2008-03-10 23:14:19

Re: Time didn't change (daylight savings)

#22 2008-03-11 00:23:30

Re: Time didn't change (daylight savings)

#23 2008-03-11 01:34:27

Re: Time didn't change (daylight savings)

#24 2008-03-11 02:04:41

Re: Time didn't change (daylight savings)

#25 2008-03-11 03:26:02

Re: Time didn't change (daylight savings)

Board footer