Control: tags -1 - moreinfo Le 2025-07-24 08:03, Ben Corby a écrit : > Date: Wed, 23 Jul 2025 08:55:54 +1000 > From: Ben Corby <bco...@new-ms.com> > To: Vincent Blut <vincent.deb...@free.fr> > Subject: Re: Bug#1109689: chrony fails on boot when using a pps device > created by gpsd > User-Agent: Evolution 3.52.3-0ubuntu1 > > Hi Vincent, thanks for getting back to me. > > sudo systemctl status chrony.service output is in attachment > chrony.status.txt.xz > > /etc/chrony/chrony.conf is in attachment chrony.conf.xz > /etc/default/gpsd is in attachment gpsd.xz > > sudo dmesg is in attachment dmesg.xz > You can see the message "PPS line discipline registered" for pps_ldisc > in this. > > sudo journalctl -t chronyd -t kernel | tail -15 is in attachment > journalctl.chronyd.txt.xz > > If you would like me to try any config change or compile any patch to > test just let me know.
So you configured chronyd so that it gets connected to gpsd using the SHM method. For this to work, you must edit the 'gpsd.service' unit to let gpsd start before chronyd. You can accomplish this using the 'systemctl edit gpsd.service' command. However, may I suggest you to use the SOCK protocol to get chronyd to connect to gpsd? It should be preferred over SHM as it offers better security. Moreover by choosing this method, you don't need to modify 'gpsd.service' as mentioned above. For example: refclock SOCK /run/chrony.ttyS0.sock refid GPS (plus any of the options supported by the refclock directive) > Cheers, > Ben. Cheers, Vincent
signature.asc
Description: PGP signature
