On 01/08/2021 20.52, Andrei Borzenkov wrote:
On 01.08.2021 21:46, Marco Calistri wrote:
Il 01/08/21 15:30, Andrei Borzenkov ha scritto:
On 01.08.2021 21:22, Marco Calistri wrote: ...
chronyc activity marco@localhost:~> chronyc activity 200 OK 0 sources online 6 sources offline 0 sources doing burst (return to online) 0 sources doing burst (return to offline) 0 sources with unknown address ... Before suspend the client is synced (see the asterisk on the NTP source).
Last time your time servers have been contacted 5 hours ago. It helps to look beyond the first column.
Before suspend all of your servers were just as well offline. This was one time sync, likely during chronyd service startup. So you do not really lose any functionality after resume, just cosmetic display change.
Not really cosmetic because if I verify my clock on https://time.is/it/ it results inaccurate and I need to manually sync chronyc.
It is cosmetic because situation after resume does not differ from situation before resume. Have you checked your clock *before* suspend? Was it synchronized?
It is possible that clock is "visibly off" after resume, as the time was set from the battery powered CMOS clock in the motherboard. The situation is the same, but before the resume the time was set from internet at least once, hours before.
Show output of
chronyc sources chronyc activity
immediately after boot.
I don't need any particular feature at the end, just would like to keep chronyc synced as it was doing ntp client that I used in the past.
chronyc does not sync anything.
chronyc does not keep time in sync as ntpd does? It is only one shot? -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))