Hi Miroslav Lichvar, I have seen an observation as chronyd syncing the system clock to old time (like 2 seconds back to the current time). Is there a way to adjust to the current time sent through the Socket.
*refclock PPS /dev/pps1 poll 0 lock GPS refid PPS trust prefer requirerefclock SOCK /var/run/chrony/udssocket.sock poll 0 refid GPS noselect* Thanks & Regards Sarveshwar.K On Mon, Mar 27, 2023 at 4:44 PM sarveshwar k <sarveshwar...@gmail.com> wrote: > Hi Miroslav Lichvar, > > Thanks for the clarification. I have tested the same to confirm. > > Thanks & Regards > Sarveshwar.K > > On Mon, Mar 13, 2023 at 12:59 PM Miroslav Lichvar <mlich...@redhat.com> > wrote: > >> On Mon, Mar 13, 2023 at 10:51:14AM +0530, sarveshwar k wrote: >> > Hi Miroslav Lichvar, >> > >> > Does "rtcsync" directive starts syncing RTC with system time >> irrespective >> > of refclocks syncing the System clock. >> >> chronyd configured with rtcsync clears the kernel "unsynchronized" >> flag (STA_UNSYNC) when the system clock is synchronized, which >> enables the kernel 11-minute system->RTC copy. You can use the >> adjtimex(8) program to verify when the status field contains 64 >> (STA_UNSYNC). >> >> > Can we configure as like below: >> > 1. Using refclocks for GPS and PPS, sync the system clock >> > 2. Once system clock is synced, RTC should be synced >> > 3. If no refclock signals available for GPS and PPS, rtcsync shall not >> > happen >> >> That's how it should work. >> >> -- >> 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. >> >>