Date: Mon, 27 Aug 2007 00:09:34 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Bill Moran <wmoran@potentialtech.com>, Modulok <modulok@gmail.com>, freebsd-questions@freebsd.org Subject: Re: time issue Message-ID: <20070827050934.GA55672@dan.emsphone.com> In-Reply-To: <20070827045528.GJ5877@tigger.digitaltorque.ca> References: <20070825024209.GG5877@tigger.digitaltorque.ca> <64c038660708242059l63288da3pc321a289df6912ed@mail.gmail.com> <20070825190440.GB9340@piglet.digitaltorque.ca> <20070825151403.2a2a247d.wmoran@potentialtech.com> <20070827045528.GJ5877@tigger.digitaltorque.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Aug 27), Michael P. Soulier said: > On 25/08/07 Bill Moran said: > > If this turns out to be your problem, I recommend using > > pool.ntp.org. Read up a bit, it should be much more reliable on a > > consistent basis. Also, OpenNTP has support built in to > > automatically talk to all of ntp.org's servers without any funky > > configuration: http://www.pool.ntp.org/use.html > > The only problem with the ntp pool is that ntp does its best to > factor out problems with specific ntp servers, by learning about > their quirks over time. An ntp pool where the specific servers that > you're talking to change regularly defeats this. ntpd does a single DNS lookup for each server at startup and doesn't shift from them even if the DNS changes, so that's not an issue. > Good enough to keep time on my server though, I suppose, since I'm > not running a cellular network. :) -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070827050934.GA55672>