Hi, Am 21.10.2022 um 18:41 schrieb Steffen Nurpmeso:
Christos Zoulas wrote in <tiufpv$fis$1%ciao.gmane.io@localhost>: |In article <3407f89f-6d30-f1a5-d013-77176f249b26%petermann-it.de@localhost>, |Matthias Petermann <mp%petermann-it.de@localhost> wrote: ... |>I use ntpd in my Qemu/nvmm VMs as a client to synchronise the (otherwise ... I would simply shoot via rdate(8) without -a, maybe via cron. Unless they are long living, then with -a. (I drive my laptop like so, against a NTP running on an always-on vserver that listens to a single NTP in the same rack.)
Thanks, I will definitely add this to my list of alternatives. Tested it successfully without the -a option (-a was not effective because of the large deviations). What I like about the approach is that it is so simple and unambiguous. At the moment I have the feeling that in my VM it triggers a small time jump of a few seconds after every cron trigger. I'll have to take a closer look at the -a option (which should prevent exactly that) and in parallel continue researching ntpd. With the latter, my experience is that - if it works - the continuity and uniformity of the time progression is very well ensured.
Kind regards Matthias