Hi Miroslav, On Thu, Apr 27, 2023 at 08:18:36AM +0530, sarveshwar k wrote: > 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.
> That looks like the initial offset of the system clock. If you restart > chronyd (but not reboot the computer) after it has been running for at > least few minutes, does the offset appear again? What can be the source for measuring this initial offset as I am not sending any data on GPS source. If I restart the chronyd as suggested, I still see the offset. This offset appears just before appearing #* on PPS source. Thanks & Regards Sarveshwar.K On Thu, Apr 27, 2023 at 1:26 PM Miroslav Lichvar <mlich...@redhat.com> wrote: > On Thu, Apr 27, 2023 at 08:18:36AM +0530, sarveshwar k wrote: > > 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. > > That looks like the initial offset of the system clock. If you restart > chronyd (but not reboot the computer) after it has been running for at > least few minutes, does the offset appear again? > > -- > 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. > >
