From owner-freebsd-questions@FreeBSD.ORG Wed Mar 2 21:23:59 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 DC1E716A4CE for ; Wed, 2 Mar 2005 21:23:59 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C3AC43D2F for ; Wed, 2 Mar 2005 21:23:59 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id j22LNwQ5086213; Wed, 2 Mar 2005 15:23:58 -0600 (CST) (envelope-from dan) Date: Wed, 2 Mar 2005 15:23:58 -0600 From: Dan Nelson To: Luke Message-ID: <20050302212357.GC77052@dan.emsphone.com> References: <20050302102908.GF30896@alzatex.com> <1529139444.20050302193225@wanadoo.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.8i 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:24:00 -0000 In the last episode (Mar 02), Luke said: > >>There's no excuse for a mailserver to not be synced to a NTP source. > >I'd extend that to apply to any server. Practically all the things a > >server does are dependent in some way on the correct time. > > I have three excuses: > 1) NTP is difficult to configure. I've done it, but it wasn't trivial. > 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. You may not know about pool.ntp.org, then. As of Sep 2004, there were 200 public servers in the pool. See http://www.pool.ntp.org/ for instructions, including a nice 4-line ntp.conf file. > 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. Two options: You can tell ntp to never step the clock by adding the -x flag, or you can increase the slew rate by fiddling with /sys/kern/kern_ntptime.c . You may need to do both. -- Dan Nelson dnelson@allantgroup.com