Date: Tue, 28 Apr 2015 12:41:37 -0500 From: Jim Thompson <jim@netgate.com> To: Christian Weisgerber <naddy@mips.inka.de> Cc: freebsd-hackers@freebsd.org Subject: Re: System clock always unsynced Message-ID: <5ABA960D-BB67-4BE8-8C55-E1B3925584FB@netgate.com> In-Reply-To: <slrnmjv91q.26os.naddy@lorvorc.mips.inka.de> References: <slrnmjsigv.8j.naddy@lorvorc.mips.inka.de> <0E68BBCF-5E21-4189-9358-F7BA3F5BECDC@netgate.com> <slrnmjv91q.26os.naddy@lorvorc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Apr 28, 2015, at 10:16 AM, Christian Weisgerber = <naddy@mips.inka.de> wrote: >=20 > On 2015-04-27, Jim Thompson <jim@netgate.com> wrote: >=20 >> Running openntpd is a poor substitute for a real ntpd. >=20 > FUD. The issues encountered when running either are well-understood, = actually. So: not FUD >> Answering, "What *does* an ntpd daemon need to do to sync the >> clock?=E2=80=9D likely requires a thesis length posting, >=20 > As it turns out, the answer to my question is a one-liner: > "STA_UNSYNC is driven by ntpd, not the kernel. Just clear the bit." It goes far beyond this, but feel free to engage as you see best. My unsolicited advice: look at phk=E2=80=99s ntimed. Jim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5ABA960D-BB67-4BE8-8C55-E1B3925584FB>