From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 28 17:41:48 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1B5E1FFD for ; Tue, 28 Apr 2015 17:41:48 +0000 (UTC) Received: from mail-ob0-f174.google.com (mail-ob0-f174.google.com [209.85.214.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DBFC91E71 for ; Tue, 28 Apr 2015 17:41:47 +0000 (UTC) Received: by obfe9 with SMTP id e9so1814970obf.1 for ; Tue, 28 Apr 2015 10:41:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=ltPojzhmqoMVf2t4XDZgHNBGKSY6RkDyr4Rra/q/G6E=; b=Jx3P+7o76b+14fsX5q2kwve6blYVVIfEbJ9WnghLuaOxB8cBEl/5f8+uR4xaESzCzL q18Q7xcXN+GyQhBpEW5DHoNDfDuus2dMGtU4Se3BJ4gtw+oyVEIHUmZi5/eXJqh7O2Q0 4qNtUllcjzxYZVSu9btzrsq2vsrhpVlgMWbTKUiiTosVvrtpWy2JxrubFBKq32j0/7MC g8UBclUjJph0Xv/YUd67SloGcnGIoXi+2V1E5VbvjLNgNtrTLgA19aUsYIv1fWJ66Rvu yaF2nnnfhimmt9Hyx9yaQdCqju5EiT+sBO3Jqb8q0eVqU8HRejHtRaDoG5omO3oVgjP2 9Erg== X-Gm-Message-State: ALoCoQm2GYEfWUciMTF73CYKZgKbAqtdlvZjOqXjat7rhXXHTdqvJChDxCxIPfusjvDAu5WE7wPx X-Received: by 10.182.243.228 with SMTP id xb4mr15538205obc.86.1430242899886; Tue, 28 Apr 2015 10:41:39 -0700 (PDT) Received: from jims-mbp.pfmechanics.com ([208.123.73.28]) by mx.google.com with ESMTPSA id qk9sm5822350obb.10.2015.04.28.10.41.39 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 Apr 2015 10:41:39 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) Subject: Re: System clock always unsynced From: Jim Thompson In-Reply-To: Date: Tue, 28 Apr 2015 12:41:37 -0500 Cc: freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <5ABA960D-BB67-4BE8-8C55-E1B3925584FB@netgate.com> References: <0E68BBCF-5E21-4189-9358-F7BA3F5BECDC@netgate.com> To: Christian Weisgerber X-Mailer: Apple Mail (2.2098) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Apr 2015 17:41:48 -0000 > On Apr 28, 2015, at 10:16 AM, Christian Weisgerber = wrote: >=20 > On 2015-04-27, Jim Thompson 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