Date: Tue, 28 Apr 2015 18:52:21 +0200 From: Christian Weisgerber <naddy@mips.inka.de> To: Ian Lepore <ian@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: System clock always unsynced Message-ID: <20150428165221.GA75198@lorvorc.mips.inka.de> In-Reply-To: <1430235252.1157.37.camel@freebsd.org> References: <slrnmjsigv.8j.naddy@lorvorc.mips.inka.de> <slrnmjsp0a.17je.naddy@lorvorc.mips.inka.de> <1430177037.1157.23.camel@freebsd.org> <20150428115741.GA68174@lorvorc.mips.inka.de> <1430235252.1157.37.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Ian Lepore: > The missing documentation you're looking for is probably RFC 1589. The > ntp_adjtime manpage probably should mention it. That looks useful, yes... Although it appears do describe an older version of the API: timex.status is described as having TIME_* clock state values and there is no trace of ORed STA_* flags. -- Christian "naddy" Weisgerber naddy@mips.inka.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150428165221.GA75198>