Date: Sat, 25 Aug 2007 15:14:03 -0400 From: Bill Moran <wmoran@potentialtech.com> To: "Michael P. Soulier" <msoulier@digitaltorque.ca> Cc: freebsd-questions@freebsd.org, Modulok <modulok@gmail.com> Subject: Re: time issue Message-ID: <20070825151403.2a2a247d.wmoran@potentialtech.com> In-Reply-To: <20070825190440.GB9340@piglet.digitaltorque.ca> References: <20070825024209.GG5877@tigger.digitaltorque.ca> <64c038660708242059l63288da3pc321a289df6912ed@mail.gmail.com> <20070825190440.GB9340@piglet.digitaltorque.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
In response to "Michael P. Soulier" <msoulier@digitaltorque.ca>: > On 24/08/07 Modulok said: > > > Is this a system that is left running 24/7 connected to the Internet, > > or a system which is frequently turned off? If the latter, you might > > It's the former. I'll try the suggested ntp sync option anyway. I'm adding > more sources too, in case the one that I'm syncing too isn't good enough. > > Ah, in fact I think that it is not. Perhaps the NRC isn't permitting public > access to their time servers anymore. 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 -- Bill Moran http://www.potentialtech.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070825151403.2a2a247d.wmoran>