From owner-freebsd-questions@FreeBSD.ORG Wed Nov 16 17:09:44 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 319D116A41F for ; Wed, 16 Nov 2005 17:09:44 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CEA143D58 for ; Wed, 16 Nov 2005 17:09:40 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id E47A75FAB; Wed, 16 Nov 2005 12:09:39 -0500 (EST) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20134-01; Wed, 16 Nov 2005 12:09:39 -0500 (EST) Received: from [192.168.1.3] (pool-68-161-122-227.ny325.east.verizon.net [68.161.122.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id D5C8D5C67; Wed, 16 Nov 2005 12:09:38 -0500 (EST) Message-ID: <437B67D9.50108@mac.com> Date: Wed, 16 Nov 2005 12:09:45 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Andrew P." References: <20051115214101.fb30f4fa.dick@nagual.st> <20051116162615.0a3b7707.dick@nagual.st> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: fbsdq Subject: Re: ntpdate 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: Wed, 16 Nov 2005 17:09:44 -0000 Andrew P. wrote: > On 11/16/05, dick hoogendijk wrote: [ ... ] >>Thank you. I >>You are probably right. I'll get rid of ntpdate in rc.conf. >>I have two timeservers at the moment. I will look for some more in the >>Netherlands. Yours are to far away ;-) > > Last time I checked ntpd docs there was no way > to tell ntpd to set the time to correct at once at > startup. Imagine that you've left your box off for a > few days. Your clock might get inaccurate by > quite a few seconds (about 2-5 minutes a month > on some hardware). > > So ntp either converges for the whole eternity, or > just fails to work. Ntpdate at startup solves this > problem. Running "ntpdate -b" at boot to forcibly syncronize the clock is a pretty good idea, but you actually can convince ntpd to sync even a clock which is badly off via: -g Normally, ntpd exits if the offset exceeds the sanity limit, which is 1000 s by default. If the sanity limit is set to zero, no sanity checking is performed and any offset is acceptable. This option overrides the limit and allows the time to be set to any value without restriction; however, this can happen only once. After that, ntpd will exit if the limit is exceeded. This option can be used with the -q option. -- -Chuck