I used to be able to run ntpd -s in 5.8 Now I can't. Apparently sometimes security causes incompatibilities.
I ran sendbug with my complaint. -Luke On Sat, May 7, 2016 at 7:06 PM, Philip Guenther <guent...@gmail.com> wrote: > On Sat, May 7, 2016 at 4:27 PM, Luke Small <lukensm...@gmail.com> wrote: > > I am running on an ASUS laptop, which OpenBSD may have disabled APM > support > > to remain compatible. Anyway, I can't run ZZZ even as root (unless there > is > > a setting that demands to be flipped somewhere). > > So here's the *real* problem, but I see no bug report for it, not even > a dmesg from you to dm...@openbsd.org. Plonk. > > > > It takes a few seconds to > > save the state and return using the virtualbox utility and it is as if > > nothing happened to stop it. What happens on another machine in which the > > battery goes out on the motherboard that powers the clock. if you > hibernate > > while you are running a preferable uninterruptible process, you are > screwed > > if your work demands an accurate clock. > > Lyndon** is correct: if you want the clock in your virtualbox to jump, > virtualbox is the one that should jump it. Changing ntpd to some how > magically detect that the VM was paused and resumed is a workaround on > a kludge. > > The output of "fortune -m tailor" seems relevant: stop walking stooped > over with your elbows bent and get a correctly fitting suit. > > > Philip Guenther > > ** Hi Lyndon! Long time since friends-of-imap dinners...
