From owner-freebsd-questions  Thu Jan 27  9:17:50 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from benge.graphics.cornell.edu (benge.graphics.cornell.edu [128.84.247.43])
	by hub.freebsd.org (Postfix) with ESMTP id 5817115750
	for <freebsd-questions@FreeBSD.ORG>; Thu, 27 Jan 2000 09:17:48 -0800 (PST)
	(envelope-from mkc@benge.graphics.cornell.edu)
Received: from benge.graphics.cornell.edu (mkc@localhost)
	by benge.graphics.cornell.edu (8.9.3/8.9.3) with ESMTP id MAA59721;
	Thu, 27 Jan 2000 12:17:47 -0500 (EST)
	(envelope-from mkc@benge.graphics.cornell.edu)
Message-Id: <200001271717.MAA59721@benge.graphics.cornell.edu>
To: mgiannoni@capu.net
Cc: freebsd-questions@FreeBSD.ORG
Subject: Re: CMOS clock and NTP 
In-Reply-To: Message from Marc Giannoni <mgiannoni@capu.net> 
   of "Wed, 26 Jan 2000 23:55:53 EST." <00012700030900.03694@yowzer.archela.net> 
Date: Thu, 27 Jan 2000 12:17:47 -0500
From: Mitch Collinsworth <mkc@Graphics.Cornell.EDU>
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


>I have a Dell Dimension P100 with a fast CMOS clock.
>This clock will gain almost an hour a day, and NTP won't 
>sync with any servers.  (I have NTP working on another host)

This is typically because xntpd won't change your clock if it is more
than some small amount wrong.  The normal setup is to run ntpdate
first to do a one-time correction, and then to start xntpd to keep
the clock in sync.

-Mitch


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message