From owner-freebsd-questions Thu Apr 6 15: 6:52 2000 Delivered-To: freebsd-questions@freebsd.org Received: from horst.bfd.com (horst.bfd.com [12.9.219.10]) by hub.freebsd.org (Postfix) with ESMTP id 07A6A37BAF4 for ; Thu, 6 Apr 2000 15:06:48 -0700 (PDT) (envelope-from ejs@bfd.com) Received: from HARLIE.bfd.com (bastion.bfd.com [12.9.219.14]) by horst.bfd.com (8.10.0/8.10.0) with ESMTP id e36M48v39102; Thu, 6 Apr 2000 15:04:08 -0700 (PDT) Date: Thu, 6 Apr 2000 15:04:08 -0700 (PDT) From: "Eric J. Schwertfeger" To: Zhihui Zhang Cc: Dan Nelson , Dave Runkle , Freebsd Questions Subject: Re: Best Time Synch Utility In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Apr 2000, Zhihui Zhang wrote: > I am wondering how to keep a cluster of PCs in sync with each other within > millisecond (loosely synchronized) even if the time of these PCs is not > synchronized well with the outside world. This can be used in a > timestamped concurrency control protocol. I wonder if ntpdate is good for > this purpose. That's what we use it for here. It just so happens that the machine that everything else is syncronizing with just happens to sync to an outside source, but as long as you set up one machine to consider its own clock a low precision, but nonetheless authoritative source, everything will sync up with that machine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message