[ntp:questions] Keeping NTP Honest Redux

Richard B. Gilbert rgilbert88 at comcast.net
Fri Nov 6 23:22:04 UTC 2009

Terje Mathisen wrote:
> Evandro Menezes wrote:
>> 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
>> the default 1024s, perhaps it'd be best to limit it to 64s.  However,
>> 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.
>> So, why was tinker maxpoll removed?  Any chance to get it back in?
> Maybe because the algorithms have been optimized to get the best 
> possible time with minimum load on the servers?
> Making it more convenient to lock polling at 64s isn't a good idea, imho.

Locking the polling interval at ANY value probably isn't a good idea. 
If not tampered with, NTPD will adjust the polling interval to the 
optimum value for the conditions then obtaining.  The conditions do change.

NTPD is at its best from about 2300 local time to 0700 local time. The 
net quiets down and NTP packets travel with minimal and highly 
predictable delays.

More information about the questions mailing list