Re[2]: NTPsec reports excessive jitter from GPSD/KPPS SHM

[Nick Burkitt]

Hi Guys.

I'm tripping over the nomenclature. Yes, PPS time is my first choice.
I feel like I only need two or three more weeks before I have a solid 
handle on the whole gpsd/ntpd thing. Unfortunately, I'm already unsure 
of how I'm going to bill the hours I've spent on it. :-)
The ntpviz web site is going away now. I'll bring it back up when I have 
a longer stretch of stats to look at. Hopefully there won't be anything 
interesting.
Thanks,

-Nick

------ Original Message ------
From: "Gary E. Miller" <address@hidden>
To: "Paul Theodoropoulos via" <address@hidden>
Sent: 3/10/2020 1:56:25 PM
Subject: Re: NTPsec reports excessive jitter from GPSD/KPPS SHM

> Yo Nick!
>
> On Tue, 10 Mar 2020 20:44:30 +0000
> "Nick Burkitt" <address@hidden> wrote:
>
> >  So moving the GPS to the end of the file AND keeping noselect is
> >  redundant?
>
> Depends.  In my case, I set a large fudge to the GPS time so that
> ntpd will only select GPS time in desperation.  YMMV.
>
> >  For my application, I'll always prefer GPS time if it's available, so
> >  removing noselect and moving it to the end is what I want?
>
> No, you will always prefer PPS time if available, then local servers,
> then regional servers, then pool servers, and last resort your GPS time.
>
> GPS time often varies by 100's of milli seconds.
>
> RGDS
> GARY
> ---------------------------------------------------------------------------
> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
> address@hidden  Tel:+1 541 382 8588
>
>             Veritas liberabit vos. -- Quid est veritas?
>     "If you can't measure it, you can't improve it." - Lord Kelvin