From owner-freebsd-questions Mon Jun 26 7:53:18 2000 Delivered-To: freebsd-questions@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 64EB337B692 for ; Mon, 26 Jun 2000 07:53:13 -0700 (PDT) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id e5QEqwn14851; Mon, 26 Jun 2000 07:52:58 -0700 (PDT) Message-Id: <200006261452.e5QEqwn14851@ptavv.es.net> To: Chris Hill Cc: Mitch Vincent , FreeBSD Questions List Subject: Re: Clocks! In-reply-to: Your message of "Sun, 25 Jun 2000 21:34:39 EDT." Date: Mon, 26 Jun 2000 07:52:58 -0700 From: "Kevin Oberman" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Sun, 25 Jun 2000 21:34:39 -0400 (EDT) > From: Chris Hill > Sender: owner-freebsd-questions@FreeBSD.ORG > > > On Sun, 25 Jun 2000, John Galt wrote: > > > NTP and/or ntpdate > > > > On Thu, 22 Jun 2000, Mitch Vincent wrote: > > > > > How are most of you keeping your clocks accurate? I'm noticing that on some > > > of the machines here we are as much as 16 minutes off actual time.. What's > > > the best (and most secure) way to keep a clock in sync with the rest of the > > > world? > > I've been using xntpd. Seems to work just fine. While xntp works fairly well, it was an experimental version of ntp (as indicated by the 'x'). You should really convert to ntp. (But read the documentation on the configuration, especially if are connected to a GPS or other reference clock.) R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message