From owner-freebsd-questions  Wed Jan 19  8:15:38 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 2D0E914CF1
	for <questions@FreeBSD.ORG>; Wed, 19 Jan 2000 08:15:36 -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 LAA92571;
	Wed, 19 Jan 2000 11:15:33 -0500 (EST)
	(envelope-from mkc@benge.graphics.cornell.edu)
Message-Id: <200001191615.LAA92571@benge.graphics.cornell.edu>
To: Sean Noonan <snoonan@cx952600-a.fed1.sdca.home.com>
Cc: questions@FreeBSD.ORG, noonans@home.com
Subject: Re: time sync problem--ntpdate AND xntpd?? 
In-Reply-To: Message from Sean Noonan <snoonan@cx952600-a.fed1.sdca.home.com> 
   of "Wed, 19 Jan 2000 08:01:03 PST." <Pine.BSF.4.21.0001190752470.2731-100000@cx952600-a.fed1.sdca.home.com> 
Date: Wed, 19 Jan 2000 11:15:33 -0500
From: Mitch Collinsworth <mkc@Graphics.Cornell.EDU>
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


>I also figured I'd use ntpdate **AND** xntpd
>on my gateway/NAT/IPFW box.  That way, I figured, my gateway/firewall box
>would get the time from a reliable time source and then the rest of my
>boxes would look to it for their time source.  Sounded good.

Yes.


>Until I read this in man ntpdate:  "Ntpdate will decline to set the date
>if an NTP server (e.g. xntpd(8)) is running on the same host".

A typical setup is to run ntpdate once during boot-up to make sure your
clock is right, and then start xntpd to keep it right.  Your plan to
then use the gateway machine to serve time for the lan is perfectly
reasonable.

-Mitch


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