From owner-freebsd-stable@FreeBSD.ORG Fri Dec 30 10:29:43 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9C4916A41F for ; Fri, 30 Dec 2005 10:29:43 +0000 (GMT) (envelope-from SRS0=MsQdwOg8=23=metro.cx=fbsd@sonologic.nl) Received: from mx1.sonologic.nl (mx1.sonologic.nl [82.94.245.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0DD243D5F for ; Fri, 30 Dec 2005 10:29:42 +0000 (GMT) (envelope-from SRS0=MsQdwOg8=23=metro.cx=fbsd@sonologic.nl) Received: from [127.0.0.1] (mx1.sonologic.nl [82.94.245.21]) (authenticated bits=0) by mx1.sonologic.nl (8.13.3/8.13.3) with ESMTP id jBUATY88077994; Fri, 30 Dec 2005 10:29:35 GMT Message-ID: <43B50C2A.9030405@metro.cx> Date: Fri, 30 Dec 2005 11:30:02 +0100 From: Koen Martens Organization: Sonologic User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Julian H. Stacey" References: <200512300039.jBU0dtYd051657@fire.jhs.private> In-Reply-To: <200512300039.jBU0dtYd051657@fire.jhs.private> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Helo-Milter-Authen: gmc@sonologic.nl, fbsd@metro.cx, mx1 Received-SPF: pass (mx1.sonologic.nl: 82.94.245.21 is authenticated by a trusted mechanism) Cc: =?UTF-8?B?RGVyZWsgS3VsacWEc2tp?= , stable@freebsd.org Subject: Re: "runtime went backwards" message in logs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2005 10:29:43 -0000 Julian H. Stacey wrote: >>PS. Not sure if this have anything to do with it (the message mentions CPU >>time, not the clock), but I'm running a ntp daemon, to synchronize time... >> >> > >Highly likely it has a Lot to do with it :-) Maybe the master time >server had `date` run manually, or otherwise shifted, or came back >on net after an outage, & the systems noticed drifted time & corrected etc. > man ntpd > man ntp.conf > etc :-) > > AFAIK, under normal circumstances ntpd should never reset the current time the hard way. Ntpd slows down (slews) or increases (steps) the speed of your clock, such that it will catch up or fall behind enough to become in line with the ntp servers it is listening to (since resetting the time the hard way is usually not a good idea; think makefiles, cronjobs that could run twice, etc..). You could check out the -x flag to nptd, to prevent setting the clock the hard way all together (since network congestion and stuff like that might result in ntpd setting the clock the hard way). Best, Koen