Re: Chrony not taking SOCKET data from Application

Hi Miroslav,

With Chrony configured using GPS and PPS refclocks I observed from "chronyc
tracking" output (filtering on "Ref time") that in each minute there is a
second missing. Any idea on what could be the cause of this? Or is this
chronyc issue.
Please provide your valuable feedback.

Attached the log file for reference.

Thanks & Regards
Sarveshwar.K

On Fri, Jun 30, 2023 at 10:33 AM sarveshwar k <[email protected]>
wrote:

> Thank you Emmanuel Bill and for the information on using makestep.
>
> On Wed, Jun 28, 2023 at 10:58 PM Emmanuel Fusté <[email protected]>
> wrote:
>
>> Le 28/06/2023 à 19:19, Bill Unruh a écrit :
>> > Why would you be using makestep if the difference were more than
>> > 100ns. That
>> > both seems extreme and totally subverts the action of chrony. Chrony is
>> > designed to correct the system clock to the best estimate of the true
>> > time and
>> > rate. Makestep ruins that, especially the rate estimate. Nothing can
>> > control
>> > the clock to 100ns unless you have very special hardware. 100ns is
>> > less than
>> > 100 ft of cable, and needs very special impedance matching to attain.
>>
>> The main problem is not the cable, but the system himself : bus latency,
>> irq latency etc...
>> You're right : very special hardware is needed to reach less than 100ns
>> measurement induced error/system clock tracking.
>>
>> Emmanuel.
>>
>> --
>> To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org
>> with "unsubscribe" in the subject.
>> For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org
>> with "help" in the subject.
>> Trouble?  Email [email protected]
>>
>>