[ntp:questions] Keeping NTP Honest Redux

Unruh unruh-spam at physics.ubc.ca
Fri Nov 6 23:04:56 UTC 2009


Evandro Menezes <evandro at mailinator.com> writes:

>I've come to the conclusion that since NTP doesn't correct for
>temperature variations, it's long-term compensation is counter-
>productive.  Therefore, instead of letting the poll period increase to

Or you could use chrony which has a much faster response to temp
variations. 
(of course this is impossible if you are using windows, but then the
effects of temp variation are below the accuracy that the operating
system is capable of anyway. If you are interested in msec accuracy, the
effects of temp variation are invisible. If you are interested in 10s of
usec then it becomes important. Do you really want usec accuracy? If so,
why are you not using local GPS to discipline your clocks?)



>the default 1024s, perhaps it'd be best to limit it to 64s.  However,

You had better do this ONLY on servers that are under your control. This
could help overload public servers. They would suddenly get 16 times as
many ntp packets, whic hcould overload them. 


>this requires that each server has the option maxpoll attached to it.
>It'd be more convenient to have set this parameter for all servers
>from a single place, such as the old tinker maxpoll option.

No idea what you want to accomplish. 


>So, why was tinker maxpoll removed?  Any chance to get it back in?

Probably so that servers did not get overloaded by people setting
maxpoll too low. 





More information about the questions mailing list