Re: gpsd + chrony + pps

[Dan Williams]

that .sock file is not the same as the /var/run/chrony.yyACM0.sock  file.

(And no, I don't think the documentation is very clear on this part.)

For time synchronization, I recommend ensuring gpsd is called with the `-n` flag, and systemd starts it on startup.  (This requires modifying the systemd file for this, which includes removing the chrony.ttyXX.sock file, and the dependencies on it.... )   Although the list might have a better way.

For reference:

1. What OS brand & version are you using? 

2. Are you running this on a RPi, or a x86 computer?

I just set this up last week with a serial/pps line + intel computer + gpsd- (3.20 / master) + chrony (2.11).   So, it definitely _CAN_ be done, but the setup can be finicky.

Daniel Williams  |  Software Engineer

dwilliams@nextdroid.com

On Fri, Jun 12, 2020 at 6:03 AM Stéphane Péneau <stephane.peneau@wanadoo.fr> wrote:

Hi!

I've made many tests to use the timepulse output on my U-blox ZED-F9P
with gpsd and chrony to get an accurate time.

I've never had a working solution if I try to use a socket like
chrony.ttyXX.sock.

But if I replace 'ttyXX' with my 'pps', it works.

refclock SOCK /var/run/chrony.pps0.sock refid PPS2 lock GNSS <== OK

refclock SOCK /var/run/chrony.ttyACM0.sock refid PPS2 lock GNSS <== NOK


Is there a mistake in the documentation ?

Stéphane