|
From: | Stéphane Péneau |
Subject: | Re: gpsd + chrony + pps |
Date: | Sat, 20 Jun 2020 15:29:17 +0200 |
User-agent: | Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 |
It's theYo Stéphane! On Fri, 19 Jun 2020 15:36:36 +0200 Stéphane Péneau <stephane.peneau@wanadoo.fr> wrote:gpsd: DEVICES="/dev/ttyS1 /dev/pps0" # Other options you want to pass to gpsd GPSD_OPTIONS="-n -b -s 115200" # Automatically hot add/remove USB GPS devices via gpsdctl USBAUTO="false"I have no idea what the above refers to, it is not part of gpsd.
/etc/default/gpsd
file used by ... a
systhingemd I won't name... ;-)root@orangepizero:~# pstree -paul | fgrep gpsdI need to know how gpsd is running, as root: # pstree -paul | fgrep gpsd # netstat -apn | fgrep 2947
root@orangepizero:~# netstat -apn | fgrep 2947
tcp 0 0 127.0.0.1:2947
0.0.0.0:* LISTEN 1/init
tcp6 0 0 ::1:2947
:::* LISTEN 1/init
chrony.conf: refclock SHM 0 refid GNSS precision 1e-1 offset 0.150 delay 0.2 noselect refclock SOCK /var/run/chrony.ttyS1.sock refid PPS2 lock GNSSWhy SHM and SOCK? They reference the same source (NMEA serial) and have the same data. That is an either/or. Why are you locking a signal to itself? I cleaned up the doc last night to make that clearer.
Maybe because it was like that in the documentation:
Let's forget this
Check out the doc as it stands today.
Yes, it' clearer now, but is a 0.9999 offset not a little high
value ?
https://gitlab.com/gpsd/gpsd/-/blob/master/www/gpsd-time-service-howto.adoc#L954
This is my new tests, following the new doc
No data with chrony.ttyS1.sock but chrony.pps0.sock is ok.
Stf
[Prev in Thread] | Current Thread | [Next in Thread] |