From owner-freebsd-questions@FreeBSD.ORG  Thu Feb 26 07:24:26 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2372916A4CE
	for <freebsd-questions@freebsd.org>;
	Thu, 26 Feb 2004 07:24:26 -0800 (PST)
Received: from sentry.24cl.com (174.113.sn.ct.dsl.thebiz.net
	[216.238.113.174])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B48F443D2F
	for <freebsd-questions@freebsd.org>;
	Thu, 26 Feb 2004 07:24:25 -0800 (PST)
	(envelope-from zlists@mgm51.com)
Received: from XPMM (unknown [63.119.50.193])
	by sentry.24cl.com (Postfix) with ESMTP id 69B9E37253;
	Thu, 26 Feb 2004 10:24:24 -0500 (EST)
Message-ID: <200402261024240582.03F5ED8D@sentry.24cl.com>
In-Reply-To: <B33A37369985DC47BAAF41511EC48078DF117F@navmmex112.corp.nt.navitaire.com>
References: <B33A37369985DC47BAAF41511EC48078DF117F@navmmex112.corp.nt.navitaire.com>
X-Mailer: Courier 3.50.00.00.1081 (http://www.rosecitysoftware.com) (P)
Date: Thu, 26 Feb 2004 10:24:24 -0500
From: "MikeM" <zlists@mgm51.com>
To: "Henning, Brian" <B.Henning@navitaire.com>,
	freebsd-questions@freebsd.org
Content-Type: text/plain; charset="us-ascii"
Subject: RE: ntpd
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2004 15:24:26 -0000

On 2/25/2004 at 3:11 PM Henning, Brian wrote:

|ntpq -c peer
|
|     remote           refid      st t when poll reach   delay   offset
|jitter
|========================================================================
|======
|+time.nist.gov   .ACTS.           1 u   26   64  377   51.856  -41.364
|20.284
|*timekeeper.isi. .GPS.            1 u   27   64  377   64.875  -25.463
|20.041
|
|I am assuming this is what you mean.
|It looks like it is working.
 =============

That's working fine.  ntp takes some time to fully "discipline" your local
clock.  You may even see "synchronization lost" messages in your log file
for up to a week.  The ntp.drift file takes up to a couple of hours to
appear.  The "unparsable" message is OK for new instances of the ntp.drift
file.  I usually install ntpd, then touch the ntp.drift file.

So long as the "reach" column shows 377, you are synch'd up and working.
The "reach" column starts at 1 and counts up to 377.  

One suggestion, though.  Do not use stratum 1 servers as your source, they
are over-busy.  Use stratum 2 servers instead. Look here for some guidance
on this topic:
http://www.eecis.udel.edu/~mills/ntp/servers.html