Re: Chrony not taking SOCKET data from Application

Hi Miroslav,

I have attached a screenshot in which I am not understanding why chrony
displaying PPS with -35ms before it moves to #*.

From the screenshot, first to outputs of "chronyc sources" displays #? for
PPS but with -35ms Last Sample. I have configured a lock on GPS for PPS.

refclock PPS /dev/pps1 poll 0 lock GPS refid PPS trust prefer require
refclock SOCK /var/run/chrony/udssocket.sock poll 0 refid GPS noselect

What can be this -35ms Last Sample mean before locking on GPS and trusting
PPS.
[image: image.png]

Thanks & Regards
Sarveshwar.K

On Tue, Mar 28, 2023 at 4:33 PM Miroslav Lichvar <[email protected]>
wrote:

> On Tue, Mar 28, 2023 at 04:17:21PM +0530, sarveshwar k wrote:
> > I have attached a screenshot of my observation. When the current time is
> > 4:11:17, the Ref time is 4:11:15 (as mentioned in tracking output).
> > [image: image.png]
>
> This is similar to the LastRx issue you reported before. The timestamp
> is intentionally adjusted by a small random value to make it more
> difficult to predict receive timestamps in the NTP symmetric mode.
> It's not necessary with a reference clock, but it's simpler do it
> always.
>
> --
> Miroslav Lichvar
>
>
> --
> 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]
>
>