From owner-freebsd-current Thu Dec 16 12:24:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1663E15047 for ; Thu, 16 Dec 1999 12:24:39 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA90822; Thu, 16 Dec 1999 13:24:37 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA73705; Thu, 16 Dec 1999 13:24:37 -0700 (MST) Message-Id: <199912162024.NAA73705@harmony.village.org> To: Poul-Henning Kamp Subject: Re: Serious server-side NFS problem Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 16 Dec 1999 18:32:44 +0100." <16722.945365564@critter.freebsd.dk> References: <16722.945365564@critter.freebsd.dk> Date: Thu, 16 Dec 1999 13:24:37 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <16722.945365564@critter.freebsd.dk> Poul-Henning Kamp writes: : If people do a "settimeofday" we change the boot time since the : amount of time we've been up *IS* known for sure, whereas the boottime : is only an estimate. There is one problem with this. The amount of uptime isn't the same as the amount of time since the machine booted. How can this happen? When a laptop suspends, it doesn't update the update while it is asleep, nor does it update the uptime by the amount of time that has been slept. IS this a bug in the apm code? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message