https://bugzilla.novell.com/show_bug.cgi?id=650460 https://bugzilla.novell.com/show_bug.cgi?id=650460#c0 Summary: Wrong system clock after changing hardware clock from local to UTC Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: vagelis_giannadakis@yahoo.gr QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=397964) --> (http://bugzilla.novell.com/attachment.cgi?id=397964) my boot.clock script (vanilla, untouched) User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.10) Gecko/20100914 SUSE/3.6.10-0.3.1 Firefox/3.6.10 When powering-on my system on November 1st (the day after the last Sunday of October, when DST zones revert to the normal zones) I noticed that my computer was displaying the old, wrong time. I adjusted the clock from within Yast, by connecting to a NTP server and rebooted, to make sure the system starts-up with the new, correct time. After rebooting, I noticed that the system clock again pointed to the old, wrong time. I decided to change my hardware clock to UTC -- I had installed openSUSE with the HC set to local -- so I rebooted, changed the hardware clock from within the computer's BIOS to UTC, changed the setting in Yast Date and Time page, re-synced with NTP and rebooted once more.. only to find out the system time was now the UTC time, instead of Greece's UTC+2! I fooled around with Yast, boot.clock and hwclock and my conclusion is that the boot.clock init script does not invoke the hwclock command to actually set the system time from the HC. In the "start|restart|reload|force-reload" section of the "case" statement, it appears to only adjust the HC with "rtc_rule /sbin/hwclock $HWCLOCK --adjust" but not actually set the system time with something like "hwclock -s $HWCLOCK". This is at least for my case, where I had initially set the HC to local time _and_then_ changed it to UTC. Maybe the installation program installs a specific version of the boot.clock script and then you basically stick with that. The workaround I have come up with, is to include the command "hwclock -s -u" in my boot.local. This seems to work fine, I guess it runs at the same stage with boot.clock. Reproducible: Always Steps to Reproduce: 1. Install with the hardware clock set to local time 2. Change the HC to UTC and reconfigure Yast 3. Reboot Actual Results: The system time is set to the hardware clock instead of the local time and zone. Expected Results: The system clock should be set to UTC plus the time difference of the local / selected time zone. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.