In article <[EMAIL PROTECTED]> Terje Mathisen <[EMAIL PROTECTED]> writes: >Dennis Hilberg, Jr. wrote: >> Hi, >> >> I have a stratum one server running ntpd [EMAIL PROTECTED] with a Garmin >> GPS 18 LVC as a refclock. I use the shmpps driver from >> http://time.qnan.org/ . Since this driver only provides the PPS signal, >> I need to have a few other servers defined in my ntp.conf so that my >> ntpd knows what time it is. >> >> Here's my concern: the poll interval on those servers is always stuck at >> the default minpoll (64sec), even though I have not specified so. I >> would rather not poll those servers at such a rapid rate, but ntpd seems >> to be doing this on its own, as far as I know. > >I think this is a known problem/bug/feature: The prefer peer responsible >for naming the PPS ticks is clamped at minpoll. In fact, if you adjust >minpoll to 4 (i.e. 16 seconds), which can be a good idea for a GPS-class >PPS signal, then you'll also lock your prefer peer at the same rate.
AFAIK it's not limited to the prefer peer - note that Dennis' ntp.conf didn't have 'prefer' on *any* of the remote servers, I believe having one used to be a requirement for a PPS-only clock to work, but apparently that has changed. I.e. if you have a reference clock, *all* remote servers will be clamped at minpoll for the reference clock. --Per Hedeland [EMAIL PROTECTED] _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
