| Re: [chrony-users] SatPulse: server-oriented alternative to gpsd for chrony |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: James Clark <jjc@xxxxxxxxxx>
- Subject: Re: [chrony-users] SatPulse: server-oriented alternative to gpsd for chrony
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Thu, 7 May 2026 16:27:18 +0200
- Cc: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1778164046; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=n+CbUWNtoOZHvUNjbVbVf/Vwht0rKiOa8bvct2qL0Ds=; b=JFZdlSy6036fdUg43srYj2nIGwo9xzY3AYxMWous4KO8HhftuVnPBoRXraWd3WLki/uRWT Lq3L80qm0ct5rUQyprnUp0DVqN5Uu2gu0bTUJGo3mvJwu6IDV0tUXfKYPQD6E9kwlnEa5Y zFZOx9vXJWRXCpayh9y3yCpKFAwuvXI=
On Fri, Apr 24, 2026 at 10:17:15AM +0700, James Clark wrote:
> I created an issue to track remaining work:
> https://github.com/jclark/satpulse/issues/256
In case you have some code ready for testing, the multi-clock MR [1]
now has a "clock" option in the refclock directive to specify the
target clock (by default it's the main system clock).
For a direct synchronization of the PHC on eth0 using a SOCK refclock
chronyd can be configured like this:
clock PHC:eth0 main
refclock SOCK /var/run/refclock.sock clock PHC:eth0 poll 0
It seems to be working nicely with ptp4l as a SOCK source (clock_servo
set to refclock_sock). If you remove the first line, it should
synchronize the system clock with the PHC left running free. This
could be an interesting alternative to phc2sys.
[1] https://gitlab.com/chrony/chrony/-/merge_requests/33
--
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.