On Sat, 7 May 2016 13:13:49 -0700 Philip Guenther <guent...@gmail.com> wrote:
> On Sat, May 7, 2016 at 9:06 AM, Luke Small <lukensm...@gmail.com> wrote: > > I often use virtualbox to run openbsd-amd64 and lately I haven't been able > > to "ntpd -s" and make it update the clock, which may have been after > > several days. > > Uh, how about we start by figuring out why "ntpd -s" is misbehaving > before we launch into adding new "NO, I REALLY MEAN IT" options? > What's the verbose output? dmesg? Had a similar "problem" on a recent install. The hardware clock was so out of date, that a ntpd -s refused to set the time because of ...ssl certificates not yet valid... Solution one disable constraint check and run ntpd the old fashioned way for the first few minutes. Or second solution, set the date once by hand and then run ntpd with constraint checks. Greetings Ben
