-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-10-29 at 22:46 +0100, Anders Johansson wrote:
Do you have your system clock set to local time? If you do, linux won't attempt to correct for DST
Any suggestions?
In linux, always set the system clock to UTC, and leave the timezone handling to the OS. Then the DST conversion will happen seamlessly
Er... in Linux the system clock always uses UTC time, regardless of what the users' settings are. It is the CMOS clock that can use UTC or Local Time, for the use of that other OS when you double boot.
A short term solution could also be to run ntpdate against a trusted ntp server, which should set your clock to the correct time again.
The NTP service always uses UTC time. It will not correct the displayed time. However, if the system clock is wrong because of mistaken assumptions during bootup setting, then yes, that will work (See * below). Don't confuse the time displayed to the user with the system internal time, which is always in UTC. Different users of the same system may have different times shown. As a side effect, there is no daylight adjustments at all to the system clock that can be done, UTC doesn't change. However, the settings of the time zone and daylight savings of each user can be modified. (*) A possibility is a mismatch in the CMOS clock having adjusted itself for daylight savings or not, booting after the hour when the change occurs, and the boot up procedure mistakenly thinking the time is in DLS or not.
But, again, setting the clock to UTC is the best long term solution
That's correct, because in that case the time setting procedure does not need logic corrections for DLS. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFRSxDtTMYHG2NR9URAi12AJ9rETke0EjKYl/nbyZ/2rH6u3KHggCeO77p ROxW0rXzelPZvcdJ9L4108E= =SZff -----END PGP SIGNATURE-----