Date: Thu, 15 May 2008 15:39:19 -0700 (PDT) From: Luke Dean <LukeD@pobox.com> To: Christopher Cowart <ccowart@rescomp.berkeley.edu> Cc: FreeBSD-Questions@FreeBSD.org Subject: Re: time drift Message-ID: <20080515153843.L77471@border.lukas.is-a-geek.org> In-Reply-To: <20080515211620.GH18488@hal.rescomp.berkeley.edu> References: <20080515185758.GA12709@ikarus.thalreit> <20080515210819.GA12605@Grumpy.DynDNS.org> <20080515211620.GH18488@hal.rescomp.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080515153843.L77471>