[ QUOTE ]
Saaby said:
I'm on a modern computer with a modern operating system that syncronizes with a time server anyway, so hopefully I won't have to worry about adjusting the time on the computer, but it's going to be a joke for all the old mainframe computers that will be off an hour -- especially since some security procedures and such require 2 computers to have the correct time set, being an hour off could break communications between the two.
I suppose it will cause a mini y2k effect -- having to fix a lot of software and programs so they're not effected by it "just in case"
[/ QUOTE ]
I have to agree that it's supremely stupid. It's unfortunate that even your "modern operating system" may have problems. Don't forget that a lot of the time calulations done by programs use the simple expedient of converting time to seconds, then subtract or add the number of seconds (3600 per hour) and then convert back to the conventional format... date and time.
That time server does not send a month, date and year. It sends an absolute value that your system has to convert to localtime. I have not checked the spec, but it's probably the number of seconds since Midnight, Jan 1, 1970, UTC.
There have been cases where the wrong people were punished because the electronic audit trail did not account for time zones. Think ATM video.
There are many electronic locks that feature a lockout for non-managers until a set time. This breaks badly when DST is played with.
Oh, well. I already sent my congress people mail explaining that it's a bad idea.
Daniel