As I said i've been using tlsdate to set time initially before running ntpd - this resolves most of the aforementioned issues and quite often being out of reach of public time-servers due to network restrictions.
On 15 September 2017 at 23:23, Stuart Henderson <s...@spacehopper.org> wrote: > On 2017-09-15, Maksym Sheremet <mshere...@sheremets.com> wrote: > > On Thu, 14 Sep 2017 23:46:14 +1200 > > Joel Wirāmu Pauling <aener...@aenertia.net> wrote: > > > >> Run NTPd on the hypervisor and NTP client In VM. Run ntpdate at boot > before > >> starting NTPd on the client to ensure the stepping is not too far off > >> first. > > > > What is the reason to run ntpdate on boot? The "-s" flag of ntpd(8) sets > time immediately at startup. > > It's rdate, not ntpdate, on OpenBSD. > > ntpd -s works as long as either A) the clock isn't too far off, or B) you > don't use the default "constraints from" option. > > >
