-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-10-30 at 09:56 -0500, Ed McCanless wrote:
OK, that part makes sense to me, but why didn't the time change automatically on Sat. night.
There different scenarios for this, and difficult to say which one applies to you. Supposing the system time was correct and the time zone correct, and the computer is running at the time, you can see the time go back one hour at the precise moment (I didn't in fact). Look: 29 Oct 01:39:01 ntpd[4353]: offset 0.060212 sec freq -45.497 ppm error 0.218041 poll 8 29 Oct 02:15:14 ntpd[4353]: synchronized to 88.*.*.23, stratum 2 29 Oct 02:28:43 ntpd[4353]: synchronized to 195.*.*.112, stratum 2 29 Oct 02:39:01 ntpd[4353]: offset 0.075185 sec freq -40.442 ppm error 0.146961 poll 9 29 Oct 02:50:26 ntpd[4353]: synchronized to 193.*.*.30, stratum 2 29 Oct 02:10:45 ntpd[4353]: synchronized to 195.*.*.112, stratum 2 29 Oct 02:12:02 ntpd[4353]: synchronized to 194.*.*.200, stratum 3 29 Oct 02:12:02 ntpd[4353]: time reset +0.248788 s 29 Oct 02:12:02 ntpd[4353]: system event 'event_clock_reset' (0x05) status 'leap_none, sync_unspec, 15 events, event_peer/strat_chg' (0xf4) See how after the 02:50:26 comes another at 02:10:45, ie, backwards? Notice that this is only the displayed time, the internal time remains unchanged, at UTC. In fact, you can have different users with different time zones, and see the time going back one hour at a different time for each one. If the computer is booted after the time change, things are different. The CMOS clock (or hardware clock) maybe set to "UTC". This is the least problematic, the boot script read the time and runs "hwclock --hctosys - --utc". No calculations needed. The CMOS clock (or hardware clock) maybe set to "local". In this case, it runs "hwclock --hctosys --localtime" instead, meaning that it has to calculate the UTC first before setting up the internal system clock. Assuming the Linux programmers did it right, and that your system time zone (the one for root) is correct, the time will be set up correctly. But you see that there are more places for error here. Now, the worst case: you booted windows before linux, and after the time shift. Windows always assumes the CMOS clock is set to local time, and noticing that the last time it was running was before the official time change, it will change it, and it will also change the CMOS clock time - so that when linux boots the time will already be shifted and it will get the incorrect time. Or any combination of the above problems. In order to check, issue the command "date" as root, and see if the time and timezones are correct for you. Ignore what kde clock says. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFRiSLtTMYHG2NR9URAt8OAJ9YbCIYi/WWR26ewySmHUg3L5L2hQCdGpWy i3pBCzt/07+AHtmtjJXocHI= =7MTk -----END PGP SIGNATURE-----