From owner-freebsd-isp Fri Jan 16 14:05:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00324 for freebsd-isp-outgoing; Fri, 16 Jan 1998 14:05:09 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from tabby.kudra.com (gw.kudra.com [199.6.44.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00319 for ; Fri, 16 Jan 1998 14:05:04 -0800 (PST) (envelope-from robert@kudra.com) Received: (from robert@localhost) by tabby.kudra.com (8.8.8/8.6.12) id QAA03016; Fri, 16 Jan 1998 16:46:17 -0500 (EST) From: Robert Sexton Message-Id: <199801162146.QAA03016@tabby.kudra.com> Subject: Re: xntpd To: mpeer@ponyexpress.gwc.cccd.edu (Michael Peer) Date: Fri, 16 Jan 1998 16:46:17 -0500 (EST) Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: <3.0.1.32.19980116113511.009c0210@rustler.gwc.cccd.edu> from "Michael Peer" at Jan 16, 98 11:35:11 am X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have played around with how it works, and not had a chance to dive into > protocol more, so sometimes it just seems magic, when it works ;) > > # > # List the sources for our time > # > server xxx.xxx.x.x # stratum x: clock you synch from > server xxx.xxx.x.x # stratum x: 2nd clock you synch from > server 127.127.1.3 # stratum 3: our own local internal clock Setting your internal clock to stratum 3 is a bad idea. It needs to be high enough (8+) That it will never be synced to in preference to accurate time. Sometimes a stratum 2 server might dip down to 3 or concievably 4 if it lost touch with its upstream peer. Even then stratum 4 or 5 time is way better than the local oscillator. There is also the possibility that you might be confused with authentic stratum 3 time by a peer. -- Robert Sexton - robert@kudra.com, Cincinnati OH, USA Cthulu 96 - Why vote for the _Lesser_ of two evils? Read the Newton FAQ!