Thanks for the clarification.
On 3/19/24 20:43, James Clark wrote:
On Wed, Mar 20, 2024 at 4:17 AM David Campbell
wrote:
Also, the device path given by chrony is out of date and the one
given
by gpsd works: that is "/run/chrony..sock" instead of
I'm just quoting the documentation.
On 3/19/24 20:29, Bill Unruh wrote:
# First option
refclock SOCK /var/run/chrony.ttyS0.sock refid GPS
On my system, /var/run is a link to /run. I think it was at least 5
years ago
that it was switeched from /var/run to /run
# Second option
refclock PPS
On Wed, Mar 20, 2024 at 4:17 AM David Campbell
wrote:
Also, the device path given by chrony is out of date and the one given
> by gpsd works: that is "/run/chrony..sock" instead of
> "/var/run/chrony.clk..sock". If I am wrong about the paths, I don't
> know how chrony works, but only the
William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273
Physics _|___ Advanced Research _| Fax: +1(604)822-5324
UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca
Canada V6T 1Z1 | and Gravity __|_theory.physics.ubc.ca/
On Tue, 19 Mar 2024,
I missed the "For example" bit, thanks for the clarification.
Reading the documentation again, I only can get the first example to
work, so there is no delay or offset.
# First option
refclock SOCK /var/run/chrony.ttyS0.sock refid GPS
# Second option
refclock PPS /dev/pps0 lock NMEA refid
On Tue, 19 Mar 2024, David Campbell wrote:
[CAUTION: Non-UBC Email]
...
Also, the device path given by chrony is out of date and the one given by
gpsd works: that is "/run/chrony..sock" instead of
"/var/run/chrony.clk..sock". If I am wrong about the paths, I don't know
how chrony
