[Bug 754329] New: Make clock handling more robust
https://bugzilla.novell.com/show_bug.cgi?id=754329 https://bugzilla.novell.com/show_bug.cgi?id=754329#c0 Summary: Make clock handling more robust Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: PC OS/Version: openSUSE 12.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: archie@dellroad.org QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 The basic problem is that the system hardware clock never gets set correctly on a newly installed system where the hardware clock's factory setting is completely wrong, even when you are running ntpd. As a result, every time the system reboots, the clock is reset back to the wrong time again. Please see Bug #699400 for a description of the problem. It is complicated and has some subtleties. However it is 100% reproducible, the cause is completely understood, and it has affected to many people as witnessed by the comments. Even so, someone marked that bug resolved/invalid. OK, if everything is working "fine", this consider this a feature request to make everything work "even better". Even though he believes the bug is invalid, in comment #40 https://bugzilla.novell.com/show_bug.cgi?id=699400#c40 Werner Fink proposes some solution(s). This issue is being filed to request those solution(s). Reproducible: Always Steps to Reproduce: 1. Set hardware clock to a crazy value 2. Boot system, enabling NTP 3. Let NTP set system (not hardware) clock correctly 4. Power cycle system 5. Clock will be set to crazy value again Bug #699400 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=754329
https://bugzilla.novell.com/show_bug.cgi?id=754329#c1
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=754329
https://bugzilla.novell.com/show_bug.cgi?id=754329#c2
--- Comment #2 from Archie Cobbs
https://bugzilla.novell.com/show_bug.cgi?id=754329
https://bugzilla.novell.com/show_bug.cgi?id=754329#c3
Dr. Werner Fink
Thanks. I have not tried the new boot.clock and ntp.
It would be prefect if you would give the new boot.clock and the ntp package a try. The ntp package includes a change in the boto scipt which should correct the hardware clock before ntpd will be started. For this the new variables NTPD_FORCE_SYNC_ON_STARTUP and NTPD_FORCE_SYNC_HWCLOCK_ON_STARTUP have been added to /etc/sysconfig/ntp. The first option does force sync of the system clock and the second one also for the hardware clock. The change in boot.clock simply determines the real offset of the hardware clock to be able to detect an offset between system and hardware clock with more the 900 seconds. You may test this on the command line with TZ=UTC /bin/date +'%s' && cat /sys/class/rtc/rtc0/since_epoch The frist command provides the system clock and the second will show the hardware clock on modern kernels. I've asked the people from bug #730374 if it is OK to add you to CC list. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=754329
https://bugzilla.novell.com/show_bug.cgi?id=754329#c4
kk zhang
participants (1)
-
bugzilla_noreply@novell.com