From owner-freebsd-current@FreeBSD.ORG Thu Feb 5 06:10:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13A9B16A4CE for ; Thu, 5 Feb 2004 06:10:08 -0800 (PST) Received: from ioskeha.hittite.isp.9tel.net (ioskeha.hittite.isp.9tel.net [62.62.156.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA09A43D58 for ; Thu, 5 Feb 2004 06:10:02 -0800 (PST) (envelope-from clefevre-lists@9online.fr) Received: from pc2k (unknown [81.185.160.179]) by ioskeha.hittite.isp.9tel.net (Postfix) with SMTP id C9BDC17BFB7; Thu, 5 Feb 2004 15:10:01 +0100 (CET) Message-ID: <077c01c3ebf1$bef1f700$7890a8c0@dyndns.org> From: "Cyrille Lefevre" To: "Poul-Henning Kamp" References: <44131.1075987208@critter.freebsd.dk> Date: Thu, 5 Feb 2004 15:10:01 +0100 Organization: ACME MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: "current @FreeBSD.org" Subject: Re: wrong kern.boottime X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2004 14:10:08 -0000 "Poul-Henning Kamp" wrote: > In message <075c01c3ebea$178b36e0$7890a8c0@dyndns.org>, "Cyrille Lefevre" write > s: > > >> >ntpd is running, so, I'm on time. > >> > >> Hmm, I'm not sure where last gets it's number from, maybe from utmp. > > > >no, from wtmp. > > > >> If the utmp record is written on boot before ntpd corrects the clock > >> that would be one explanation... > >> > >> Either way, I'm pretty sure that kern.boottime contains what it should > >> contain: Our best estimate of the time when the system was booted. > > > >absolutely not, the real boot time was the wtmp time which is the same > >as /var/run/dmesg.boot. > > > >a proof of the real boot time : > > > ># bzgrep Accounting /var/log/messages.* > >messages.2.bz2:Feb 1 21:40:43 gits kernel: Accounting enabled > > This is only a proof if the machine was NTPD'synced at this time. > > If your CMOS clock was a couple of days off, your system would boot with > that time, and not until NTPD gets its act together would the clock > be stepped to the right time. > > This is still the best theory I can come up with. > from /var/log/ntplog, there have been only a correction of less than 2 secs : Feb 1 21:40:43 gits ntpdate[9394]: step time server 138.195.130.71 offset 1.880536 sec Feb 1 21:40:47 gits ntpd[57196]: ntpd 4.1.1b-a Fri Jan 30 19:17:34 CET 2004 (1) Feb 1 21:40:47 gits ntpd[57196]: kernel time discipline status 2040 Feb 1 21:55:00 gits ntpd[57196]: time set 0.125300 s Feb 1 22:10:10 gits ntpd[57196]: time reset -0.202478 s Feb 1 22:47:45 gits ntpd[57196]: time reset 0.276161 s Feb 1 23:02:54 gits ntpd[57196]: time reset -0.156614 s Feb 1 23:40:25 gits ntpd[57196]: time reset 0.834652 s Feb 1 23:55:47 gits ntpd[57196]: time reset -0.531431 s Cyrille Lefevre. -- mailto:clefevre-lists@9online.fr