Refclock quirk

[Hal Murray]

I'm seeing things like this:
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+fe80::21e:c9ff: .PPS.            1 u   86 1024  377    0.483   -3.643   0.330
+fe80::226:2dff: .PPS.            1 u  758 1024  377    0.582   -3.652   0.392
+fe80::226:2dff: 192.168.1.33     2 u  802 1024  377    0.591   -3.632   0.362
*GPS_NMEA(0)     .GPS.            0 l   21   64  377    0.000   74.403   5.791
oPPS(0)          .PPS.            0 l   84 1024  377    0.000   -3.750   0.332
+glypnod         .PPS.            1 u   45   64  377    0.361   -3.683   0.012
+shuksan         .PPS.            1 u   60   64  377    0.313   -3.656   0.021
+mon             .PPS.            1 u   39   64  377    0.552   -3.801   0.034
+tom             .PPS.            1 u   31   64  377    0.506   -3.770   0.037
+cent            .PPS.            1 u   31   64  377    0.442   -3.729   0.014

That's on a raspberry Pi with a GPS HAT.  The glitch is the 1024 polling 
interval for the PPS.  That shouldn't be there.  Note that the NMEA driver is 
at 64.

I don't remember seeing anything like that before your recent refclock 
changes.

There is a maxpoll 6 on the 5 servers after the PPS.  Nothing on the first 3 
or either refclock.

I thought the refclocks used to set their own polling interval, but I can't 
find that code.  (I remember changing something many years ago.)



-- 
These are my opinions.  I hate spam.