-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2008-10-21 at 17:02 -0400, Bob S wrote:
Well it looks like the system clock runs on local time and it also looks like the ntp server is setting local time.
Not really. The system time is UTC (actually not, but lets assume it is, close enough), but the difference to local time is applied when displaying the time. The NTP servers give UTC time, too: this way you can use NTP server from anywhere in the world. It is the CMOS clock which can be local or UTC time; local for compatibility with windows. If you never boot into windows, it is best if you tell Yast that bios keeps UTC time, not local. Less problems.
I did this a little after midnight. (UTC -4)(Eastern Daylight Time)
Easystreet:/ # ntpdate clock.isc.org 22 Oct 00:26:06 ntpdate[4625]: adjust time server 204.152.184.72 offset -0.123777 sec Easystreet:/ # hwclock --show ; date ; date -u Wed 22 Oct 2008 12:26:17 AM EDT -0.789944 seconds Wed Oct 22 00:26:16 EDT 2008 Wed Oct 22 04:26:16 UTC 2008 Easystreet:/ # hwclock --systohc Easystreet:/ # rm /etc/adjtime Easystreet:/ #
I do have "that other OS" on a small drive but haven't booted it in over a year.
And, I rebooted into the bios and the time was correct and then let it continue to boot into SuSE and lost four hours. Then rebooted into the bios and it showed the lost 4 hours, then let it finish booting into Suse and lost another four hours. Something in the start-up script?
strange. grep HWCLOCK /etc/sysconfig/clock It should say "--localtime". Look also at the "TIMEZONE" and "DEFAULT_TIMEZONE" settings on the same file. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkj/p7gACgkQtTMYHG2NR9UjgQCcDM7eT8Rjxy2AGXwVxHcLsLo+ 3swAni0uIdnhVMm2HWkCGZznmanR2FsC =ewgR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org