From owner-freebsd-stable Fri Feb 20 14:30:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15787 for freebsd-stable-outgoing; Fri, 20 Feb 1998 14:30:52 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA15748 for ; Fri, 20 Feb 1998 14:30:35 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0y60xP-00021c-00; Fri, 20 Feb 1998 15:30:11 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id PAA18268; Fri, 20 Feb 1998 15:30:30 -0700 (MST) Message-Id: <199802202230.PAA18268@harmony.village.org> To: Dennis Tenn Subject: Re: xntp messages in new build Cc: Scot Elliott , stable@FreeBSD.ORG In-reply-to: Your message of "Fri, 20 Feb 1998 11:34:47 EST." References: Date: Fri, 20 Feb 1998 15:30:30 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk In message Dennis Tenn writes: : | Feb 20 15:34:16 uranus xntpd[16462]: Previous time adjustment didn't : | complete : : All it means AFAIK is it couldn't connect to the time server to update the : clock. This happens on my system too and you shouldn't worry about it. No. That's not quite right. It means that the last adjustment (via tickadj) didn't finish slowly skewing the clock before the next one was requested. I've seen this mostly when there is a largish offset at the start. You can ignore these messages if you have a couple, but thery may indicate something wrong with your hardware (or that of the time server) if you get lots of them. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message