Date: Mon, 27 Aug 2007 00:55:28 -0400 From: "Michael P. Soulier" <msoulier@digitaltorque.ca> To: Bill Moran <wmoran@potentialtech.com> Cc: freebsd-questions@freebsd.org, Modulok <modulok@gmail.com> Subject: Re: time issue Message-ID: <20070827045528.GJ5877@tigger.digitaltorque.ca> In-Reply-To: <20070825151403.2a2a247d.wmoran@potentialtech.com> References: <20070825024209.GG5877@tigger.digitaltorque.ca> <64c038660708242059l63288da3pc321a289df6912ed@mail.gmail.com> <20070825190440.GB9340@piglet.digitaltorque.ca> <20070825151403.2a2a247d.wmoran@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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. Good enough to keep time on my server though, I suppose, since I'm not running a cellular network. :) Mike -- Michael P. Soulier <msoulier@digitaltorque.ca> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFG0llAKGqCc1vIvggRAl1RAKCmafqnQ2tdv6l9SqVxlwOKBTyu5wCfch+o YiMa6xI8IStxi4WxqafetOA= =XZeS -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070827045528.GJ5877>