From owner-freebsd-hackers@FreeBSD.ORG  Mon Apr 27 17:04:04 2015
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 04B75C8F
 for <freebsd-hackers@freebsd.org>; Mon, 27 Apr 2015 17:04:04 +0000 (UTC)
Received: from mail-in-01.arcor-online.net (mail-in-01.arcor-online.net
 [151.189.21.41])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "mx.arcor.de", Issuer "Thawte SSL CA" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id AEE111F82
 for <freebsd-hackers@freebsd.org>; Mon, 27 Apr 2015 17:04:03 +0000 (UTC)
Received: from mail-in-01-z2.arcor-online.net (mail-in-01-z2.arcor-online.net
 [151.189.8.13])
 by mx.arcor.de (Postfix) with ESMTP id 3lbBR13npxz2lrL
 for <freebsd-hackers@freebsd.org>; Mon, 27 Apr 2015 18:30:05 +0200 (CEST)
Received: from mail-in-06.arcor-online.net (mail-in-06.arcor-online.net
 [151.189.21.46])
 by mail-in-01-z2.arcor-online.net (Postfix) with ESMTP id 7E0F57DC99B
 for <freebsd-hackers@freebsd.org>; Mon, 27 Apr 2015 18:30:05 +0200 (CEST)
X-Greylist: Passed host: 188.104.143.26
X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-06.arcor-online.net 3lbBR11v9vz8FYQ
Received: from lorvorc.mips.inka.de
 (dslb-188-104-143-026.188.104.pools.vodafone-ip.de [188.104.143.26])
 by mail-in-06.arcor-online.net (Postfix) with ESMTPS id 3lbBR11v9vz8FYQ
 for <freebsd-hackers@freebsd.org>; Mon, 27 Apr 2015 18:30:05 +0200 (CEST)
Received: from lorvorc.mips.inka.de (localhost [127.0.0.1])
 by lorvorc.mips.inka.de (8.14.9/8.14.9) with ESMTP id t3RGU3be040740
 for <freebsd-hackers@freebsd.org>; Mon, 27 Apr 2015 18:30:03 +0200 (CEST)
 (envelope-from news@lorvorc.mips.inka.de)
Received: (from news@localhost)
 by lorvorc.mips.inka.de (8.14.9/8.14.9/Submit) id t3RGU2nE040739
 for freebsd-hackers@freebsd.org; Mon, 27 Apr 2015 18:30:02 +0200 (CEST)
 (envelope-from news)
To: freebsd-hackers@freebsd.org
From: Christian Weisgerber <naddy@mips.inka.de>
Newsgroups: list.freebsd.hackers
Subject: Re: System clock always unsynced
Date: Mon, 27 Apr 2015 16:30:02 +0000 (UTC)
Lines: 12
Message-ID: <slrnmjsp0a.17je.naddy@lorvorc.mips.inka.de>
References: <slrnmjsigv.8j.naddy@lorvorc.mips.inka.de>
X-Trace: lorvorc.mips.inka.de 1430152202 40559 ::1 (27 Apr 2015 16:30:02 GMT)
X-Complaints-To: usenet@mips.inka.de
User-Agent: slrn/1.0.2 (FreeBSD)
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Apr 2015 17:04:04 -0000

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?

-- 
Christian "naddy" Weisgerber                          naddy@mips.inka.de