From owner-freebsd-stable Fri Oct 9 09:47:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02932 for freebsd-stable-outgoing; Fri, 9 Oct 1998 09:47:07 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02919 for ; Fri, 9 Oct 1998 09:47:00 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id JAA23355; Fri, 9 Oct 1998 09:46:29 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <361E3DE4.39F057F4@gorean.org> Date: Fri, 09 Oct 1998 09:46:28 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5b2 [en] (X11; I; FreeBSD 2.2.7-STABLE-0929 i386) X-Accept-Language: en MIME-Version: 1.0 To: Marc Gutschner CC: freebsd-stable@FreeBSD.ORG Subject: Re: Is 'xntpd' broken in -stable? References: <361DEC25.30065DCC@Triplan.COM> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Gutschner wrote: > If I try to fire up 'xntpd' on > the FreeBSD box as a client, it reads the config, tells me something > about initial adjustment values, forks and (seems to) dies That "something" it tells you is actually valuable diagnostic info. It's telling you that xntpd can't set the time because it's so far off now that xntpd can't handle it. So, before you start xntpd you need to issue an 'ntpdate whatever.your.primary.time.host.is' then you should be able to start xntpd. Good luck, Doug -- *** Chief Operations Officer, DALnet IRC network *** Go PADRES! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message