[ntp:questions] LOCL clock reachability not 377?

A C agcarver+ntp at acarver.net
Tue Jul 29 20:07:00 UTC 2014

On 2014-07-29 12:46, William Unruh wrote:
> On 2014-07-29, A C <agcarver+ntp at acarver.net> wrote:
>> On 2014-07-29 11:33, William Unruh wrote:
>> [1] ATOM's own documentation suggest maxpoll of 4 to 6 to keep the clock
>> synced to PPS.  But that pins everything else to the same value unless a
>> minpoll is set on the other servers.  However, once minpoll is set, the
>> combination of the pinning by ATOM plus the forced required minpoll
>> means the external servers never change polling period nor do they get
>> the opportunity to start at the short 64s polling interval during
>> initial daemon startup and then ramp to some comfortable value in the
>> 1000 second range.
> Is that really right? I would have expected each clock source to have
> its own minpoll/maxpoll, independent of any other source. Are you sure
> that is not the case?

Check the source code, it's in there.  It pins the maxpoll for all
sources and also won't let the poll time climb or drop.  I had to pull
that part out so I wouldn't hammer outside servers while still using my
local PPS source.

More information about the questions mailing list