Problem migrating from legacy to ntpsec

[Jim Pennino]

    On Saturday, September 14, 2024 at 12:06:55 PM PDT, Hal Murray <halmurray at sonic.net> wrote:  
 
 
Jim Pennino said:
>    ntpq now reports:
>    xNMEA(0)    .GPS.    0 l    9  16  377  0.0000    -96.4123  0.5949
>    xPPS(0)      .PPS.    0 l    8  16  377  0.0000    0.4051  0.0235 

>    Adjusting time1 appears to do nothing.

Adjusting time2 on the NMEA line should reduce that -96 in the offset 
column.
Note time2 vs time1.

The PPS stuff won't kick in until the x on the NMEA line turns into a *.  
You need to get the offset small enough and/or add something like:
  tos mindist 0.075 # default is 0.001 (1 ms)


-- 
These are my opinions.  I hate spam.



My point was that ntpd is now magically processing all data again, i.e. reach is now 377 for both after the latest batch of updates.
I probably should have explicitly said that, my bad.

As for the offsets, I have scripts that analyze that and after everything that has gone on it will take a couple of days to stabilize to something statistically valid.




  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/users/attachments/20240914/edcf76ac/attachment-0001.htm>