Date: Tue, 23 Feb 2010 20:19:47 +1100 From: Peter Jeremy <peterjeremy@acm.org> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: freebsd-stable@freebsd.org Subject: Re: ntpd struggling to keep up - how to fix? Message-ID: <20100223091947.GA44123@server.vk2pj.dyndns.org> In-Reply-To: <20100222114105.GA96234@icarus.home.lan> References: <20100217200322.da66c9f8.torfinn.ingolfsen@broadpark.no> <20100218205458.GA78560@server.vk2pj.dyndns.org> <20100218231223.ec6b9fa8.torfinn.ingolfsen@broadpark.no> <20100219003844.acdaa866.torfinn.ingolfsen@broadpark.no> <20100220015351.GB81639@server.vk2pj.dyndns.org> <20100220223201.178e67dd.torfinn.ingolfsen@broadpark.no> <20100221050823.GB22670@server.vk2pj.dyndns.org> <4b82483e.5OXNba8%2BJ2F18v3D%perryh@pluto.rain.com> <20100222111810.GD12891@server.vk2pj.dyndns.org> <20100222114105.GA96234@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
--gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2010-Feb-22 03:41:05 -0800, Jeremy Chadwick <freebsd@jdc.parodius.com> w= rote: >ntpd under normal operation (not +/- 500ppm) "figure out" on its own the >average amount of drift, which is what ntpd.drift is for, correct? Yes. It takes a long time for ntpd to characterise the local system clock. Once it does so, it stores the calculated drift in ntp.drift and updates it every hour or so. This means that when ntpd is restarted, it can immediately set its PLL to a reasonably close value, rather than starting from scratch. --=20 Peter Jeremy --gBBFr7Ir9EOA20Yy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkuDnbMACgkQ/opHv/APuIfE5wCePr4FejMFiw4RDV4Wii3xWqtI sFsAnRInukSAgdJXdHtKnaKn13dmsltk =nPGv -----END PGP SIGNATURE----- --gBBFr7Ir9EOA20Yy--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100223091947.GA44123>