https://bugzilla.novell.com/show_bug.cgi?id=699400 https://bugzilla.novell.com/show_bug.cgi?id=699400#c14 --- Comment #14 from Robert Davies <rob.opensuse.linux@googlemail.com> 2011-07-11 14:40:52 UTC --- (In reply to comment #11)
Normally the CMOS clock is set only once to UTC and all works flawless. Setting the CMOS clock to localtime is a user error (and IMHO we should not support this anymore as Windows7[tm] can handle UTC im CMOS).
For broken hardware you loose as there is no chance to correct anything.
I tested Windows 7 running with UTC, as it is my preference. The problem is it is not acceptable to users, because the time shown "localtime" is then UTC, with additional clock in true localtime. Setting Windows local time clock to Europe/London GMT/BST wiith DST and "additional clock" to be UTC, causes the out by an hour problem!! MS HAVE not properly supported, system clock in UTC BUT insist in doing DST, and non DST adjustment means it's not localtime. sntp -s on boot, did indeed fix up the Linux clock, as well as CMOS clock and allow NTP to operate & synchronise from there on. No 11 minute mode, if it's done before the NTP daemon is even started. Frankly I cannot see why, an "sntp -s" with 2 or 3 defined servers, is not simply done on boot anyway, the CMOS clock is not nearly as accurate as NTP protocol. Doing that EVERY time simplifies the rcntp script to. -- 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.