From owner-freebsd-questions@FreeBSD.ORG Thu May 15 22:39:33 2008 Return-Path: Delivered-To: FreeBSD-Questions@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3ECB11065671 for ; Thu, 15 May 2008 22:39:33 +0000 (UTC) (envelope-from LukeD@pobox.com) Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com [207.106.133.19]) by mx1.freebsd.org (Postfix) with ESMTP id 0E5298FC2F for ; Thu, 15 May 2008 22:39:32 +0000 (UTC) (envelope-from LukeD@pobox.com) Received: from localhost.localdomain (localhost [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id B1F2E3EA5; Thu, 15 May 2008 18:39:31 -0400 (EDT) Received: from lukas.is-a-geek.org (pool-71-113-78-181.sttlwa.dsl-w.verizon.net [71.113.78.181]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id B572B3EA2; Thu, 15 May 2008 18:39:25 -0400 (EDT) Date: Thu, 15 May 2008 15:39:19 -0700 (PDT) From: Luke Dean X-X-Sender: lukas@border.lukas.is-a-geek.org To: Christopher Cowart In-Reply-To: <20080515211620.GH18488@hal.rescomp.berkeley.edu> Message-ID: <20080515153843.L77471@border.lukas.is-a-geek.org> References: <20080515185758.GA12709@ikarus.thalreit> <20080515210819.GA12605@Grumpy.DynDNS.org> <20080515211620.GH18488@hal.rescomp.berkeley.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Pobox-Relay-ID: C905CDCE-22CF-11DD-A876-80001473D85F-96347044!a-sasl-fastnet.pobox.com Cc: FreeBSD-Questions@FreeBSD.org Subject: Re: time drift X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Luke Dean List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 22:39:33 -0000 On Thu, 15 May 2008, Christopher Cowart wrote: > David Kelly wrote: >> Its PC commodity-grade. Not all that unusual even for stuff sold >> claiming to be a "server". This is in no small part why ntpd exists. >> >> nptd calculates a correction coefficient and (under FreeBSD) stores it >> in /var/db/ntpd.drift for use on next start so as to more quickly >> establish a lock. >> >> So in short ntpd calibrates your clock in order to minimize the >> corrections required. Is The Right Thing To Do. > > We run a large number of FreeBSD servers under vmware. We've seen ntpd > silently die, because the drift becomes "insane." What do others do in > this situation? (We've resorted to croning ntpdate for VMs.) kern.hz="100" in /boot/loader.conf solved this problem for me.