Hello By measuring tool, I understand you only want chrony to report the current GPS time. If that's true, then have a look at the option -x which prevents chrony from setting the system time. Then you still need a way to get the time from the chrony daemon. You could use an ntp client to do so. Or maybe chronyc has a command to query the time of the chrony daemon ?
Regards, Hubert Le jeu. 16 févr. 2023 à 05:34, sarveshwar k <sarveshwar...@gmail.com> a écrit : > Hi Miroslav Lichvar, > > Can you please provide below information: > Is it not possible to achieve synchronization accuracy less than 100ns > with chrony (with GPS and 1PPS). > Can we configure chrony behaving as a measurement tool (not to make any > corrections)? > > Thanks & Regards > Sarveshwar.K > > On Tue, Feb 7, 2023 at 2:05 PM Miroslav Lichvar <mlich...@redhat.com> > wrote: > >> On Tue, Feb 07, 2023 at 12:04:53PM +0530, sarveshwar k wrote: >> > > The reason for chronyc sources sometimes showing 2 as LastRx, even >> > > when no samples are lost, seems to be incorrect rounding of the sample >> > > time. I can fix that. >> > >> > Will there be a release for this fix. >> > Current version I am using is 3.5 of chrony for which yocto recipe >> exists. >> >> It will be in the next release. Backport the commit dec07aa844f8 from >> the chrony repository to 3.5 shouldn't be too difficult. It's not >> actually a bug, but rather a data-minimization feature which is not >> necessary for reference clocks. >> >> -- >> Miroslav Lichvar >> >> >> -- >> To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org >> with "unsubscribe" in the subject. >> For help email chrony-users-requ...@chrony.tuxfamily.org >> with "help" in the subject. >> Trouble? Email listmas...@chrony.tuxfamily.org. >> >>
