| Re: [chrony-users] Chrony on CM4 |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Chrony on CM4
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 4 Sep 2023 15:47:01 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1693835240; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=LmKAHTbs1U7vwjAaPwaAOVE/WJLHXWjYU3+BXPgSuEc=; b=QutoOsEGAQPMqsbpYoEi8hoZA1YDzcS9VEVCTOT4n0v8SR8x4RABm7pombsr0fhuEs9Vxi oiIww2q53HDh/sDNEK+j6DbN40eKtaOu38VKjMxr3hUiwdvq2N+wQjl1Ag6FUEIqYt2Jhs yDB6Xa0Hg2bCMhs3Q4Eamg/QWOM2qvA=
On Mon, Sep 04, 2023 at 08:23:13PM +0700, James Clark wrote:
> On Mon, Sep 4, 2023 at 3:46 PM Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
>
> > The latest gpsd version supports SOCK for message-based timing data,
> > which can replace SHM 0.
>
> I was using gpsd 3.25 (as included in Fedora 38), which appears to be
> the latest version, and SOCK didn't work for me.
The latest gpsd should try to connect to two different sockets:
/run/chrony.XXX.sock
/run/chrony.clk.XXX.sock
where XXX is the device name. The first one is for PPS, the second one
for message-based timing.
--
Miroslav Lichvar
--
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.