From owner-freebsd-hackers Wed Aug 22 21:43:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 86A5B37B407 for ; Wed, 22 Aug 2001 21:43:40 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.4/8.11.4) with ESMTP id f7N4hQn46653; Thu, 23 Aug 2001 06:43:30 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: Thierry Herbelot , hackers@FreeBSD.ORG Subject: Re: clock synchronization quality via NTP ? In-Reply-To: Your message of "Wed, 22 Aug 2001 20:42:41 MDT." <200108230242.f7N2gfW80510@harmony.village.org> Date: Thu, 23 Aug 2001 06:43:26 +0200 Message-ID: <46651.998541806@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200108230242.f7N2gfW80510@harmony.village.org>, Warner Losh writes: >: More precisely : is it reasonable to hope having a system clock not >: farther from the GPS clock by more than 50 micro-seconds ? 50 microseconds should be feasible provided that you either provide a very stable temperature or replace the 14.318 MHz xtal on the motherboard with a something more stable. >PC hardware really sucks for timing. Tell me about it... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message