From owner-freebsd-current@FreeBSD.ORG Thu Feb 5 03:56:36 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 64C7A16A4CE for ; Thu, 5 Feb 2004 03:56:36 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2350143D31 for ; Thu, 5 Feb 2004 03:56:34 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i15BuVDF042698; Thu, 5 Feb 2004 12:56:31 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: "Cyrille Lefevre" From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 05 Feb 2004 12:43:02 +0100." <06ef01c3ebdd$36b53190$7890a8c0@dyndns.org> Date: Thu, 05 Feb 2004 12:56:31 +0100 Message-ID: <42697.1075982191@critter.freebsd.dk> 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 11:56:36 -0000 In message <06ef01c3ebdd$36b53190$7890a8c0@dyndns.org>, "Cyrille Lefevre" write s: >> ># last reboot >> >reboot ~ Sun Feb 1 21:41 >> ># ls -l /var/run/dmesg.boot >> >< >> >-rw-r--r-- 1 root wheel 5547 Feb 1 21:40 /var/run/dmesg.boot >> ># sysctl kern.boottime >> >kern.boottime: { sec = 1075812223, usec = 350585 } Tue Feb 3 13:43:43 2004 >> ># uname -a >> >FreeBSD gits 5.2-CURRENT FreeBSD 5.2-CURRENT #1: Sat Jan 31 15:17:05 CET 2004 >> > >> >any idea ? >> >> What does "date" say on your machine ? > ># date -u >Thu Feb 5 11:39:36 UTC 2004 ># date >Thu Feb 5 12:39:39 CET 2004 ># ls -l /etc/wall_cmos_clock >-rw-r--r-- 1 root wheel 0 Jun 9 2001 /etc/wall_cmos_clock > >ntpd is running, so, I'm on time. Hmm, I'm not sure where last gets it's number from, maybe from utmp. 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. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.