I'm really surprised I can't find this anywhere, but I've been all over google and the NTP doc site and can't find anything. I'm using ntpd and it didn't adjust my clock for daylight savings time. I've read that it does it slowly so as to not throw off processes that rely on time, but it's been over 12 hours and it's still exactly an hour ahead of the actual time. Is there a setting somewhere I missed to tell it about daylight savings?

Is your hardware clock set to UTC or local time?

Lyle.

I'm pretty sure it's local time, although I'm not 100% sure. "date -u" correctly shows UTC, if that means anything.

Post the output of:

cat /etc/hardwareclock

Things work a lot smoother if you set your hardware clock to UTC. Daylight savings time changes work automatically.

NPT doesn't care about your time zone of if you've switched to or from daylight savings time; it only concerns itself with UTC.

Lyle.

localtime

So how does the time change work then if NTP doesn't do it? What was that I read about it making small adjustments until the change was complete?

The few reasons I think I had for keeping it stored as localtime: 1) I saw something in the kernel config asking how it was stored, and I've had enough of kernel recompiles lately, 2) If I remember correctly, it's easy to run into a situation with Windows and Linux fighting over the time if the hardware is set to UTC, as in adjusting it to different times each time you reboot (I rarely use Windows but I keep it on the computer for certain apps that don't work otherwise and would rather not have to deal with that).

So is there no way to make it work automatically the way it's currently set up?

glibc takes care of converting UTC to localtime; it has a database of timezone information it consults to present you with the correct local time. The correct local time could be different for different users logging into your machine from around the world. I guess it does some kind of workaround if your hardwareclock set to localtime.

I don't think there is a way to make it work automatically without setting it to UTC. Go on, it won't hurt much. Windows at least asks before it changes the time; just click "No" when it asks if you ever boot into Windows. The time will be wrong in Windows though. I think modern versions of Windows can work with the hardware clock set to UTC anyway.

Even if you have CONFIG_APM_RTC_IS_GMT set to yes, it won't be that big of a deal (your clock might be out by a few seconds after your computer wakes up.) Next time remember not to set this. This only affects Advanced Power Management (APM.)

Lyle.

If you have a dual boot machine linux/windows and the linux clock RTC is set to local time, let windows do the change of time and reboot after that into linux.
It is the simpler way to fix this matter.

Ok that works. Still, I read something about ntpd handling it and making the change slowly so it doesn't mess anything up... was I just interpreting that wrong?

I think what you read was about adjusting the speed of the system clock slowly if it is too slow or too fast. It is not about DST change of time.