From owner-freebsd-questions@FreeBSD.ORG Thu Mar 3 02:15:29 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 319BF16A4CE for ; Thu, 3 Mar 2005 02:15:29 +0000 (GMT) Received: from smtp11.wanadoo.fr (smtp11.wanadoo.fr [193.252.22.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7B2943D1D for ; Thu, 3 Mar 2005 02:15:28 +0000 (GMT) (envelope-from atkielski.anthony@wanadoo.fr) Received: from me-wanadoo.net (unknown [127.0.0.1]) by mwinf1103.wanadoo.fr (SMTP Server) with ESMTP id 7F50C1C0008E for ; Thu, 3 Mar 2005 03:15:27 +0100 (CET) Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3]) by mwinf1103.wanadoo.fr (SMTP Server) with ESMTP id 5C20E1C00087 for ; Thu, 3 Mar 2005 03:15:27 +0100 (CET) X-ME-UUID: 20050303021527377.5C20E1C00087@mwinf1103.wanadoo.fr Date: Thu, 3 Mar 2005 03:15:27 +0100 From: Anthony Atkielski X-Priority: 3 (Normal) Message-ID: <165579735.20050303031527@wanadoo.fr> To: freebsd-questions@freebsd.org In-Reply-To: References: <20050302102908.GF30896@alzatex.com> <1529139444.20050302193225@wanadoo.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Received mail timestamp is off by 7 hours X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 02:15:29 -0000 Luke writes: > 1) NTP is difficult to configure. I dunno. I configured it in a few minutes on my test box. > 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. There must be thousands of such sites. Heck, Windows ships with an NTP client that it uses to synchronize automatically--although by default it only queries the server once a week, instead of once ever few minutes as it should (PC clocks are so notoriously bad in keeping time that there's no way a clock would stay correct for an entire week). > 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. I haven't noticed any problem at all. FreeBSD is especially adept at tinkering in a discreet way that doesn't harm anything. It gradually slews the clock instead of stepping it, and nothing on the machine is affected by the slight changes. My LAN is synchronized with some pretty extraordinary accuracy thanks to NTP, which runs on the main server. The other two machines synchronize from this main server. I have about a dozen servers in the config that the machine polls periodically (not very often now, since the daemon has a pretty good idea of the drift on my system clock). -- Anthony