From owner-freebsd-current Sun Jan 2 12:19:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 7BCC614C15 for ; Sun, 2 Jan 2000 12:19:32 -0800 (PST) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Sun, 2 Jan 2000 12:19:31 -0800 From: "David Schwartz" To: "Karl Denninger" , "Poul-Henning Kamp" Cc: Subject: RE: xntpd - VERY old folks, how about updating? :-) Date: Sun, 2 Jan 2000 12:19:30 -0800 Message-ID: <000501bf555e$ad254190$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <20000102104932.B23036@Denninger.Net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That sucks severely - NONE of the common units have the PPS output?! > > Barf. Oh well. Many of them do, but it's still not meant for precision timekeeping and the exact relationship between its PPS pulse edges and UTC's second boundaries may not be precisely specified. It's not a good idea to use a GPS unit not specifically made for timing as an NTP reference clock. Sorry to plug myself, but I offer a GPS timing unit that is made specifically for timing use. It's $375 (quantity one) and more info is available at http://www.gpsclock.com/ PPS output is specified as +/- 1 us of UTC second boundary. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message