No problem. After ntpd has ran for a while, it will write a drift file, and you'll have one for next time you start up. In the meantime, ntpd will need to fully calibrate the clock drift of your system.
On 2016 Apr 26 (Tue) at 10:51:41 -0700 (-0700), bluesun08 wrote: :/etc/ntpd.conf: : :# $OpenBSD: ntpd.conf,v 1.14 2015/07/15 20:28:37 ajacoutot Exp $ :# :# See ntpd.conf(5) and /etc/examples/ntpd.conf : :servers pool.ntp.org :sensor * :constraints from "https://www.google.com"; : :__________________________________________ : :/var/log/messages: :ntpd[32440]: /var/db/ntpd.drift is empty : :Whats the problem here? : : : : :-- :View this message in context: http://openbsd-archive.7691.n7.nabble.com/var-db-ntpd-drift-is-empty-tp294914.html :Sent from the openbsd user - misc mailing list archive at Nabble.com. : -- "Thirty days hath Septober, April, June, and no wonder. all the rest have peanut butter except my father who wears red suspenders."
