From owner-freebsd-questions@FreeBSD.ORG Mon May 7 23:53:54 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C4B7A16A40B for ; Mon, 7 May 2007 23:53:54 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by mx1.freebsd.org (Postfix) with ESMTP id 8EF1213C45B for ; Mon, 7 May 2007 23:53:54 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 5021851944 for ; Mon, 7 May 2007 19:53:53 -0400 (EDT) Date: Tue, 8 May 2007 00:53:50 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20070508005350.45d53438@gumby.homeunix.com.> In-Reply-To: References: <20070503014137.I3544@duane.dbq.yournetplus.com> <20070503015723.S3544@duane.dbq.yournetplus.com> <4639FAB6.9050701@mac.com> <20070504171053.41eddb6a@gumby.homeunix.com> <7967B2A8-3FF5-46AD-AFEA-9EE5C680A414@mac.com> <20070507230246.198b6608@gumby.homeunix.com.> X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.12; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Time Synchronizing Between Two Servers X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2007 23:53:54 -0000 On Mon, 7 May 2007 18:35:13 -0500 Jeffrey Goldberg wrote: > On May 7, 2007, at 5:02 PM, RW wrote: > > > If the time error is zeroed by ntpdate, and there's a drift-file, I > > don't see that the actual drift value makes much difference. I > > suspect that any quartz clock is overkill. > > As someone already mentioned, drift data doesn't really solve the > problem if the amount of drift varies (often with temperature, and > sometimes dramatically with sleep). The clock on my wife's G5 iMac > seems to be erratic, but I haven't (and won't) bother to investigate > further. If her system is up to 2 seconds off for a bit after > waking from sleep, so be it. (If I ever start using kerberos around > the house, I will have to address that.) > > If a machine is up for months, ntpdate may have been run in the > distant past, so you can still a fair amount of error. > > ntpd is really a very light weight thing. When things are ticking > over nicely, it may make just one query every few hours and still > keep very good time. I was questioning the need for a low-drift system clock on a machine that *is* running ntpd, not the need for ntpd.