[BC] DST for the rest of you

[richardbrianjohnson at verizon.net]

 Hmmm,
properly configured Microsoft and Linux machines handle the TZ change well. If the automation software gets confused it is __broken__ and the company who produced it needs to fix it.
 
I write software that keeps event logs with microsecond resolution and a time-change means __nothing__ because it is only when the internal tick is printed out that any software even cares and it's only a TZ based variable that determines how the time is displayed. The internal timer tick just continues and is slowly adjusted to track whatever network server you have specified as a time-server.

Wall clocks of course are different. However, even modern digital clocks set/reset the time after 2:00 AM on the appropriate day. If the station doesn't have a live operator at 2 AM, who cares??? It should be a non-event. However, I've noticed that RDS time on some FM stations in the Boston area is broken for several days after the time change.

Worcester's WSRS always seems to get it right.
 
 Cheers,
Richard B. Johnson
http://www.AbominableFirebug.com
 
On 11/01/13, Barry Mishkind<barry at oldradio.com> wrote:
 
If you are not on the BDR Newsletter list
( http://lists.theBDR.net/mailman/listinfo/bdr )
you may need to get the reminder about the
clock change on Sunday morning.

Yes, most of you get to sleep in another hour, but
you may have to spend more than that hour fixing
clocks and servers.