Re[2]: NTP with only GPS/PPS flags PPS as falseticker

[Nick Burkitt]

Hi Gary.

Maybe I'm having problems with terminology again. The ntpmon output I 
sent showed a value of 0 in the "reach" column for every row except 
SHM(0) and SHM(2). If that's not "no reach," then could you explain what 
you mean by the term?
Thanks,

-Nick

------ Original Message ------
From: "Gary E. Miller" <address@hidden>
To: address@hidden
Sent: 3/16/2020 4:19:09 PM
Subject: Re: NTP with only GPS/PPS flags PPS as falseticker

> Yo Nick!
>
> On Sat, 14 Mar 2020 22:38:09 +0000
> "Nick Burkitt" <address@hidden> wrote:
>
> >  I need to tweak my ntpd.conf so that ntpd will use GPS and PPS when
> >  no network is available. As it is now, GPS is never used, and when
> >  all other clock sources go away, PPS is marked with the fatal 'x' as
> >  well.
>
> Your ntpmon shows you did not wait long.  Your other sources still had
> "reach".  Ntpd operates very, very slowly.  Let us know what you see
> when everything but the SHM()s have no reach.
>
> Simple lack of patience is the largest problem new users have.
>
> >  Here's my current ntp.conf
>
> ntpd has a setting called "minsane".  It is the minimum sane tickers
> before it will steer the local clock.  The default is 1, and you
> did not over ride it.  So as long as ntpd sees a good SHM(2) then
> you should be good.  After givng tnpd time to settle.
>
> >    99.104.170.138  132.163.97.6     2 u 1160  128    0 86.471ms
>                                                ^^^
>
> Note the reach!
>
> 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