From owner-freebsd-questions@FreeBSD.ORG Sat Aug 25 19:14:05 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3ADE716A417 for ; Sat, 25 Aug 2007 19:14:05 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from mail.potentialtech.com (internet.potentialtech.com [66.167.251.6]) by mx1.freebsd.org (Postfix) with ESMTP id EF92713C469 for ; Sat, 25 Aug 2007 19:14:04 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from vanquish.pitbpa0.priv.collaborativefusion.com (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.potentialtech.com (Postfix) with ESMTP id DE4C3EBC78; Sat, 25 Aug 2007 15:14:03 -0400 (EDT) Date: Sat, 25 Aug 2007 15:14:03 -0400 From: Bill Moran To: "Michael P. Soulier" 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> X-Mailer: Sylpheed 2.4.4 (GTK+ 2.10.14; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org, Modulok Subject: Re: time issue X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2007 19:14:05 -0000 In response to "Michael P. Soulier" : > 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