Re: gpsd + chrony + pps

[Gary E. Miller]

Yo Stéphane!

On Thu, 18 Jun 2020 21:50:40 +0200
Stéphane Péneau <stephane.peneau@wanadoo.fr> wrote:

> Le 18/06/2020 à 21:24, Gary E. Miller a écrit :
> >> For the socket method, i can't use chrony.tty***.sock it doesn't
> >> work  
> > Not expected.  What is the failure mechanism?  
> Chrony doesn't receive any signal from the PPS socket (unreachable).
> I don't have the real value available right now, but I can recreate a 
> setup in a few days if needed.

That would be helpful, otheerwise we are jsut guessing.

> The gpsd documentation says :
> 
> "To get chronyd to connect to gpsd using the more precise socket
> method add this to your chrony.conf file (replacing ttyXX with your
> device name)."

Yes, I edited that.  "precise" should be be there, the socket is
just different, not more precise.

> So, my device name was...hmmm my gnss receiver is available on
> ttyACM0, so let's put "chrony.ttyACM0.sock" inside chrony.conf.

yes.

> But "chrony.ttyACM0.sock" seems wrong.

Why?  It is the basename() of the device the receiver is on.

> As Perhaps this would be clearer :
> 
> "To get chronyd to connect to gpsd using the more precise socket
> method add this to your chrony.conf file (replacing ttyXX with your
> PPS device name ; if your pps is /dev/pps0, replace ttyXX with pps0)

Not an if, but an and.  But I think I get the gist.  I'll ponder.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        gem@rellim.com  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

pgpkMgT8N1uTb.pgp
Description: OpenPGP digital signature