From owner-freebsd-current Thu Dec 16 12:37:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id E143414FBB for ; Thu, 16 Dec 1999 12:37:11 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id MAA07676; Thu, 16 Dec 1999 12:37:02 -0800 (PST) Date: Thu, 16 Dec 1999 12:37:02 -0800 (PST) From: Tom Bartol To: Warner Losh Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-Reply-To: <199912162024.NAA73705@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Dec 1999, Warner Losh wrote: > 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 > IIRC it does update uptime properly after a suspend in 2.2.8 but does not do so in 3.X and -current on my ThinkPad 770. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message