From owner-freebsd-questions Fri Apr 7 1:31:12 2000 Delivered-To: freebsd-questions@freebsd.org Received: from maxim.gba.oz.au (gba.tmx.com.au [203.9.155.249]) by hub.freebsd.org (Postfix) with SMTP id 25E3D37BBFE for ; Fri, 7 Apr 2000 01:31:06 -0700 (PDT) (envelope-from gjb-freebsd@gba.oz.au) Received: (qmail 16308 invoked by uid 1001); 7 Apr 2000 15:13:31 +1000 X-Posted-By: GBA-Post 2.02.01 12-Dec-1999 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Message-Id: Date: Fri, 07 Apr 2000 15:13:30 +1000 From: Greg Black To: David Kelly Cc: FreeBSD-questions@FreeBSD.ORG Subject: Re: Kernel adjustment for clock drift References: <200004070124.UAA11635@nospam.hiwaay.net> In-reply-to: <200004070124.UAA11635@nospam.hiwaay.net> of Thu, 06 Apr 2000 20:24:53 EST Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Kelly writes: > See my other posting to this list. I ran xntpd for years on a dialup > connection. Connected an hour or two or three per day. Xntpd doesn't > seem to have any problems resuming when the connection resumes. The machine in question typically connects for around five minutes at a time, about once per day. When I attempted to use xntpd in that scenario a couple of years ago, it would not play. Perhaps it has been changed since then, but it would surprise me if it could do much in that sort of window. (That's why I want to tune the kernel's timekeeping to better match reality, because I can then use ntpdate on each connection and all will be well.) However, if you think xntpd can now perform adequately even with such short and widely-spaced connections, perhaps you could say so. If so, I might give it another try. Thanks. -- Greg Black -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message