| I talked to the customer that Glenn was working with and came up
with these answers, please let me know if I'm off base:
< * how often is the server polled?
According to the log files, 35 seconds is the minimum, and the synch
can occur as little as 35 seconds apart. Customer also saw this with
packet trace.
< * how does ntp handle daylight saving time?
< immediately? gradually?
If the server's clock is set immediately, then the clients' clocks
are also set almost immediately as soon as synch occurs. Since on VMS,
system manager has to set the clock forward/back manually, he could
gradually change the clock on the server source.
< * is there a range or value for being off from the
< time server? What happens if it's exceeded.
None I'm aware of, but there has been some talk about it in the notes
about being off for more than 24 hours...
Jay
|
| > < * how does ntp handle daylight saving time?
> < immediately? gradually?
> If the server's clock is set immediately, then the clients' clocks
> are also set almost immediately as soon as synch occurs. Since on VMS,
> system manager has to set the clock forward/back manually, he could
> gradually change the clock on the server source.
I don't think this is true. As far as I know, the timestamps put on the
wire are all in UTC. This means there is no change when DST happens. DTS is
only meaningful for the local node (different nodes in your network can be
in different timezones).
As far as I know, the UCX NTP implementation doesn't handle DST. You need
operator intervention to change the time.
Regards,
Oswald
|