From owner-freebsd-questions@FreeBSD.ORG Wed Mar 2 21:18:03 2005 Return-Path: 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 A7FFF16A4CE for ; Wed, 2 Mar 2005 21:18:03 +0000 (GMT) Received: from mirapoint2.tis.cwru.edu (mirapoint2.TIS.CWRU.Edu [129.22.104.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F96F43D1D for ; Wed, 2 Mar 2005 21:18:03 +0000 (GMT) (envelope-from ttt@cwru.edu) Received: from [129.22.151.155] (tagon.ENGINEERING.CWRU.Edu [129.22.151.155]) by mirapoint2.tis.cwru.edu (MOS 3.5.4-GR) with ESMTP id DNI19173 (AUTH ttt); Wed, 2 Mar 2005 16:17:50 -0500 (EST) Message-ID: <42262D74.3050907@cwru.edu> Date: Wed, 02 Mar 2005 16:17:40 -0500 From: Tom Trelvik User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: LukeD@pobox.com References: <20050302102908.GF30896@alzatex.com> <1529139444.20050302193225@wanadoo.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: Received mail timestamp is off by 7 hours X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 21:18:03 -0000 Luke wrote: > 1) NTP is difficult to configure. I've done it, but it wasn't trivial. It's always seemed rather straightforward to me, what in particular gave you trouble, perhaps we could help? > 2) Finding an NTP server willing to accept traffic from the public isn't > easy either. For me it involved a scavenger hunt through out-of-date > websites and a lot of failed attempts. time.nist.gov is public, and has it's own atomic clock. A google search for "public ntp servers" also found this: http://www.pool.ntp.org/ > 3) If your clock tends to run noticably fast or slow, constant NTP > corrections tend to do more harm than good, at least in my experience. > It got to where I couldn't even run a buildworld because NTP kept > tinkering with the clock in the middle of the process. That suggests larger problems on your system, to me, but I dunno. Tom