Il 03/08/21 12:20, Carlos E. R. ha scritto:
On 03/08/2021 17.04, Marco Calistri wrote:
Il 02/08/21 02:08, Andrei Borzenkov ha scritto: ...
This below is the solution to avoid loosing the sync of chrony during st/by and resumes:
Explanation:
The makestep directive can be used to allow chronyd to step the clock. For example, if chrony.conf had
makestep 1 3
the clock would be stepped in the first three updates if its offset was larger than one second. Normally, it’s recommended to allow the step only in the first few updates, but in some cases (e.g. a computer without an RTC or virtual machine which can be suspended and resumed with an incorrect time) it may be necessary to allow the step on any clock update. The example above would change to
makestep 1 -1
https://chrony.tuxfamily.org/faq.html#_is_code_chronyd_code_allowed_to_step_... Notice that some sources (ex. vmware) say that it is not correct to use an ntp daemon inside a virtual machine. Instead, a single daemon should run on the host, and the time be synced from the host to all guests. This should be done by virtual machine deamon that connects the guest to the host, name varies depending on the virtualization method.
In my case I'm using chrony on the host machine not virtual. As I told at the beginning, my system was loosing the ntp sync with external sources during the st/by periods. So far, after I changed the configuration file as inicated before, my host keeps clock synced. Regards, -- Marco Calistri Build: openSUSE Tumbleweed 20210801 Kernel:5.13.4-1-default Desktop: XFCE (4.16.0)