From owner-freebsd-stable@FreeBSD.ORG Fri Dec 30 00:39:57 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 56E4F16A41F for ; Fri, 30 Dec 2005 00:39:57 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DA0A43D46 for ; Fri, 30 Dec 2005 00:39:56 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A7FD0.dip.t-dialin.net [84.154.127.208]) (authenticated bits=0) by tower.berklix.org (8.12.9p2/8.12.9) with ESMTP id jBU0dqtQ028292; Fri, 30 Dec 2005 01:39:53 +0100 (CET) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id jBU0daYh020140; Fri, 30 Dec 2005 01:39:46 +0100 (CET) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id jBU0dtYd051657; Fri, 30 Dec 2005 01:39:55 +0100 (CET) (envelope-from jhs@fire.jhs.private) Message-Id: <200512300039.jBU0dtYd051657@fire.jhs.private> To: =?ISO-8859-2?Q?Derek_Kuli=F1ski?= In-Reply-To: Message from =?ISO-8859-2?Q?Derek_Kuli=F1ski?= of "Thu, 29 Dec 2005 14:44:32 PST." <1445969398.20051229144432@takeda.tk> Date: Fri, 30 Dec 2005 01:39:55 +0100 From: "Julian H. Stacey" Cc: 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 00:39:57 -0000 > 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 :-) -- Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com Mail in Ascii, HTML=spam. Ihr Rauch = meine allergischen Kopfschmerzen.