Re: [chrony-users] Setting up Chrony with PPS

[ Thread Index | Date Index | More Archives ]

> On 19/02/2016, at 4:41 PM, Tomalak Geret'kal <tom@xxxxxxxxx> wrote:
> On 19/02/2016 03:08, Bryan Christianson wrote:
>> My understanding is that chrony.ttyAMA0.sock is a socket created by chronyd and listened to by chronyd When gpsd starts, it checks to see if the socket exists and writes the PPS data to it.
> Isn't that backwards? How would gpsd know what socket to write to?
> Generally the model is the writer (which doesn't know what wants to receive) creates the file and the receiver (which knows what it wants to receive) opens it.
> We can see that here by the presence of gpsd.sock.
> Right?
> Tom

Yes - I agree it does seem a little odd, but for good reason


"gpsd, when run as root, feeds reference clock information to chronyd using a socket named /var/run/chrony.ttyXX.sock (where ttyXX is replaced by the GPS receiver’s device name. This allows multiple GPS receivers to feed one chronyd.

No gpsd configuration is required to talk to chronyd. chronyd is configured using the file /etc/chrony.conf or /etc/chrony/chrony.conf. Check your distributions documentation for the correct location. To get chronyd to connect to gpsd using the basic ntpd compatible SHM method add this to use this basic chrony.conf file:”

i.e. gpsd uses a naming convention and the socket as configured in chronyd also uses that same convention

Bryan Christianson

To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.

Mail converted by MHonArc 2.6.19+