[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: DST change and home auto...



Dan Lanciani wrote:
> In article <4611a979$1_1@xxxxxxxxxxxxxx>, lgardner@xxxxxxxxxxxxxxxxxxxxxxxxxx (Lewis Gardner) writes:
> | Dan Lanciani wrote:
> | > In article <46112082$1_1@xxxxxxxxxxxxxx>, lgardner@xxxxxxxxxxxxxxxxxxxxxxxxxx (Lewis Gardner) writes:
> | >
> | > | I manage several networks running mostly XP pro all syncing to local
> | > | Linux servers running NTP. The problem is that M$ in their wisdom
> | > | allowed machines syncing to a LOCAL time server to calculate DST offsets
> | > | at the machine level. This is madness.
> | >
> | > What else could they do?  Are you suggesting that there is some way to
> | > get timezone information from an NTP server (local or otherwise)?
> |
> | Not exactly.
> |
> | My feeling is that if you specify a machine as the timeserver on the
> | subnet (especially a private IP range) then the client machines should
> | use the time they receive without adjustment. In most cases this is what
> | the network admin needs. Letting the local machines "fiddle" with
> | timezones and DST adjustments causes more problems than it solves.
>
> The time you get from an NTP server (local or otherwise) is UTC.  If
> you use that time without adjustment you will be running GMT.
>
> 				Dan Lanciani
> 				ddl@danlan.*com

EXACTLY!  NTP isn't just "something somebody came up with and put in the
public domain" but is a defined spec - like FTP, SMTP, SNMP, IP, TCP, etc!


comp.home.automation Main Index | comp.home.automation Thread Index | comp.home.automation Home | Archives Home