Date: Mon, 27 Apr 2015 17:23:57 -0600 From: Ian Lepore <ian@freebsd.org> To: Christian Weisgerber <naddy@mips.inka.de> Cc: freebsd-hackers@freebsd.org Subject: Re: System clock always unsynced Message-ID: <1430177037.1157.23.camel@freebsd.org> In-Reply-To: <slrnmjsp0a.17je.naddy@lorvorc.mips.inka.de> References: <slrnmjsigv.8j.naddy@lorvorc.mips.inka.de> <slrnmjsp0a.17je.naddy@lorvorc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2015-04-27 at 16:30 +0000, Christian Weisgerber wrote: > On 2015-04-27, Christian Weisgerber <naddy@mips.inka.de> wrote: > > > What *does* an ntpd daemon need to do to sync the clock? > > Okay, let me rephrase this since the first two replies completely > missed the point. This is an API programming question. How is the > poorly documented ntp_adjtime() API to be used so the system clock > will lose the STA_UNSYNC status and switch from TIME_ERROR to TIME_OK > as clock state? > It requires a call to ntp_adjtime() with the MOD_STATUS bit set in ntv.modes and the STA_UNSYNC bit clear in ntv.status. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1430177037.1157.23.camel>