Mike Bartman wrote:
As you note, NTP deals only with UTC. There is no
provision in the code
for dealing with time zones or or standard vs. daylight
time and I would
be extremely surprised if anyone on the development team would be
willing to add such a thing.
I would put it much stronger than that. This would go against
the whole
architecture of NTP. Timezone information including Daylight Savings
Time is a local phenomenon. That's what a GUI or even a command line
would display to the user. To change this would violate the
NTP protocol
and cause massive dislocation of reliable time distribution. Think
locally. Your clients get the NTP packets and turn them into
local time.
NTP uses UTC between servers and between servers and clients (same NTPD
in both cases of course)...that doesn't mean that the code can't be
aware of timezones or DST. Our port of NTP does exactly that, since
unlike Unix, OpenVMS systems usually have the system clock set to local
time, not UTC, and so there is no "at display time" conversion of the
time and NTPD needs to know the local time to set the system clock
properly.
That has not been true for years! Years ago VMS did not support
anything but local time. DECUS members kicked Digital's butt around
1994-1995 and got support for time zones. It may be that not all System
Administrators make use of the feature but the systems I worked with
since VMS V6.2 (ca. 1997) certainly did.
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
