From owner-freebsd-questions Mon Apr 29 9:32:45 2002 Delivered-To: freebsd-questions@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id C30EE37B41B for ; Mon, 29 Apr 2002 09:32:38 -0700 (PDT) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.12.2/8.12.3) with ESMTP id g3TGWZ2Z002889; Mon, 29 Apr 2002 11:32:37 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.2/8.12.2/Submit) id g3TGWYOs002850; Mon, 29 Apr 2002 11:32:34 -0500 (CDT) Date: Mon, 29 Apr 2002 11:32:34 -0500 From: Dan Nelson To: "Daniel O'Connor" Cc: SNFettig , freebsd-questions@FreeBSD.ORG Subject: Re: Clock adjustment? Message-ID: <20020429163234.GP77779@dan.emsphone.com> References: <1020084497.10959.1.camel@chowder.dons.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1020084497.10959.1.camel@chowder.dons.net.au> User-Agent: Mutt/1.3.28i X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Apr 29), Daniel O'Connor said: > On Mon, 2002-04-29 at 21:55, SNFettig wrote: > > The way that I have set this up is by following the cheat-sheet > > from Dan O'Connor > > (http://www.mostgraveconcern.com/freebsd/ntp.html)*. Over time I > > have made tweaks from other howto areas on the net, but this is > > pretty much it: > > Oops.. I forgot to mention.. > > I can't really use ntp as the system isn't dialed up very frequently > (ie about an hour a day maximum) and I currently use ntpdate to > adjust the date at each dialup. > > The cumulative difference is around 120 seconds. I was recently > informed that you can adjust the machdep.i8254_freq sysctl which > should do what I want.. If you add the 'iburst' flag to your server lines in ntp.conf, ntpd will send 8 packets the first time it sees a server is reachable, and should adjust the system's clock within 30 secs. Hopefully if you are on for an hour ntpd will be able to calculate your system's clock drift on its own (and store it in /etc/ntp.drift). 120 secs/day is pretty bad drift, though. Ntpd might resort to stepping the clock like ntpdate, but since it is also going to be slewing it while you're offline, the step shouldn't be as large as if you were just using ntpdate. http://www.eecis.udel.edu/~ntp/ntpfaq/NTP-s-config.htm#AEN2453 http://www.eecis.udel.edu/~ntp/ntp_spool/html/assoc.htm -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message