Date: 25 Mar 2002 20:14:16 +0100 From: Dag-Erling Smorgrav <des@ofug.org> To: Chip Morton <tech_info@threespace.com> Cc: FreeBSD Chat <chat@freebsd.org>, phk@freebsd.org Subject: Re: ntpd configuration Message-ID: <xzpofhca29j.fsf@flood.ping.uio.no> In-Reply-To: <4.3.2.7.2.20020325114426.01e0bdf8@threespace.com> References: <4.3.2.7.2.20020324112056.0199b938@threespace.com> <20020322200120.D17681@rain.macguire.net> <20020323033242.31E383F29@bast.unixathome.org> <4.3.2.7.2.20020324112056.0199b938@threespace.com> <4.3.2.7.2.20020325114426.01e0bdf8@threespace.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chip Morton <tech_info@threespace.com> writes: > I did notice that Dan Langille's ntp.conf had multiple server lines in > it, so I'm trying that in my file as well to see if it helps. Using multiple servers allows ntpd to compensate for network artifacts etc. (such as assymetric routing) that are specific to any one server. It doesn't give you perfect time but does help reduce the margin of error. > By the > way, how often does ntpd update the time by default? It tries to measure your computer's clock drift relative to the server(s) and passes those measurements on to the kernel so it can compensate for the measured drift, so it should not "update the time" per se except at startup, unless the hardware clock is too erratic. Check your logs; ntpd will issue a message whenever it needs to actually step the clock (rather than just skewing it), as well as when it gives up trying to keep your clock accurate (which it most likely did if your clock got as far as seven minutes off). I've Cc:ed Poul-Henning as he knows way more about this than I do. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpofhca29j.fsf>