[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strange ntpmon offset
From: |
Gary E. Miller |
Subject: |
Re: Strange ntpmon offset |
Date: |
Mon, 29 Nov 2021 12:26:48 -0800 |
Yo Massimiliano!
On Mon, 29 Nov 2021 20:37:01 +0100
Massimiliano Fago <massimiliano.fago@gmail.com> wrote:
> gpsd: 3.22 (revision 3.22)
Almost 2 years old. 3.23.1 is current.
> ntpmon ntpsec-1.2.0+ 2021-04-20T14:25:51Z (git rev 1feb8f90d)
Better, but 1.2.1 is current.
> my gps is u-blox and I have an external antenna. MAX-M8Q-0
Good enough for timekeeping.
> my ntp.conf file is:
>
> refclock shm unit 1 minpoll 4 maxpoll 4 refid PPS flag4 1 prefer
> # GPS Serial data reference (NTP0)
> #server 127.127.28.0 minpoll 4 maxpoll 4
> #fudge 127.127.28.0 time1 0.9999 refid GPS
> refclock shm unit 0 time1 -0.0900 refid GPS flag4 1 noselect
Where are the other chimers? ntpd will not work with just 1 chimers.
You ntp.conf is missing the pool statement.
> My problem is that I have strange value on offset data.
Dunno why you think that is strange. Your ntpd is not locked, so it not
driving your local clock, so the offset will vary randomly with temperature
> Please give me some suggestion.
RTFM:
https://gpsd.io/gpsd-time-service-howto.html
https://gpsd.io/gpsd-time-service-howto.html#_feeding_ntpd_from_gpsd
https://gpsd.io/time-service-intro.html
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
gem@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can't measure it, you can't improve it." - Lord Kelvin
pgpUmy0HDnXms.pgp
Description: OpenPGP digital signature