Subject | Late DST 2007 patch on Windows 2000 server with Firebird 1.5 |
---|---|
Author | Nikita Nikitich |
Post date | 2007-03-27T20:11:28Z |
All,
Recently I had to patch a Windows 2000 server running Firebird 1.5
for a 2007 Daylight Saving Time. I had to do it March 21st, when DST
was already in effect, and the machine's clock was one hour behind.
Before applying the patch I noticed that for whatever reason DST
checkbox was unchecked in the Control Panel. In case it matters,
timezone is PST.
I used .reg and .vbs files as described in a Microsoft KB article.
Then I restarted w32time service to make sure new settings take
effect. When I opened control panel again, DST checkbox was already
checked, and the clock was showing correct time. I also verified
using tzedit.exe that DST dates are updated.
Now the wierd thing. Though machine's clock was correct, 'NOW'
function in firebird was still one hour behind. And I noticed it
only one day later. Stopping and restarting Firebird service solved
the problem. But I still don't understand how this happened and keep
wondering if the same thing will happen in November.
Can anyone explain what happened and should I worry about the
future "fall backs" and "spring forwards"?
Thank you!
Recently I had to patch a Windows 2000 server running Firebird 1.5
for a 2007 Daylight Saving Time. I had to do it March 21st, when DST
was already in effect, and the machine's clock was one hour behind.
Before applying the patch I noticed that for whatever reason DST
checkbox was unchecked in the Control Panel. In case it matters,
timezone is PST.
I used .reg and .vbs files as described in a Microsoft KB article.
Then I restarted w32time service to make sure new settings take
effect. When I opened control panel again, DST checkbox was already
checked, and the clock was showing correct time. I also verified
using tzedit.exe that DST dates are updated.
Now the wierd thing. Though machine's clock was correct, 'NOW'
function in firebird was still one hour behind. And I noticed it
only one day later. Stopping and restarting Firebird service solved
the problem. But I still don't understand how this happened and keep
wondering if the same thing will happen in November.
Can anyone explain what happened and should I worry about the
future "fall backs" and "spring forwards"?
Thank you!