gpsd-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Nick Burkitt
Subject: Re[2]: NTP with only GPS/PPS flags PPS as falseticker
Date: Tue, 17 Mar 2020 01:21:36 +0000
User-agent: eM_Client/7.2.37929.0

Hi Gary.

I'd really like to understand what's happening before investing the time to change over to chrony. Although it may be the best long-term solution. I think the problem is that ntpd always flags my GPS as a falseticker, so when the network time sources go away, it may be left with no tickers, rather than one.

-Nick

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

Yo Nick!

On Tue, 17 Mar 2020 00:48:52 +0000
"Nick Burkitt" <address@hidden> wrote:

 I waited about 48 hours. I didn't save the ntpmon output at that
 stage, but the GPS offset had grown to over 100 seconds.

Ouch.  It should have grabbed one of the SHM()s long before that.

Anything in the ntp logs?

Maybe try to force minsane to 1?

What version of NTPsec?  Have you tried chrony?  ntpd was never
designed for intermittent or off net operation.  Try chronyd, it was
designed with your use case in mind.

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]