From owner-freebsd-stable Fri Feb 20 10:58:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13185 for freebsd-stable-outgoing; Fri, 20 Feb 1998 10:58:16 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from prefetch.san.rr.com (ns1.san.rr.com [204.210.0.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13124 for ; Fri, 20 Feb 1998 10:57:55 -0800 (PST) (envelope-from Studded@san.rr.com) Received: from san.rr.com (dt050ndd.san.rr.com [204.210.31.221]) by prefetch.san.rr.com (8.8.7/8.8.8) with ESMTP id KAA17533; Fri, 20 Feb 1998 10:55:08 -0800 (PST) Message-ID: <34EDD18A.4F5DE3D5@san.rr.com> Date: Fri, 20 Feb 1998 10:55:06 -0800 From: Studded Organization: Triborough Bridge and Tunnel Authority X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-STABLE-0220 i386) MIME-Version: 1.0 To: Scot Elliott CC: stable@FreeBSD.ORG Subject: Re: xntp messages in new build References: <34EDA335.4BDADC31@planet-three.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Scot Elliott wrote: > > Hi. I did a cvsup yesterday of the current Stable source, and built world. > Now I'm getting syslog messages from xntpd. And clues? > > Feb 20 15:34:16 uranus xntpd[16462]: Previous time adjustment didn't > complete Check your clock to see if it's close to the correct time. I've had problems sometimes after a reboot where the clock was so far off that xntpd refused to adjust it. A quick ntpdate fixed me right up. Hope this helps, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message