From owner-freebsd-current  Thu Dec 16 13: 5:56 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 75D011581D
	for <freebsd-current@FreeBSD.ORG>; Thu, 16 Dec 1999 13:05:53 -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 NAA08234; Thu, 16 Dec 1999 13:05:45 -0800 (PST)
Date: Thu, 16 Dec 1999 13:05:45 -0800 (PST)
From: Tom Bartol <bartol@salk.edu>
To: Warner Losh <imp@village.org>
Cc: freebsd-current@FreeBSD.ORG
Subject: Re: Serious server-side NFS problem 
In-Reply-To: <199912162054.NAA74098@harmony.village.org>
Message-ID: <Pine.BSF.4.10.9912161257350.36287-100000@eccles.salk.edu>
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 <Pine.BSF.4.10.9912161244160.36287-100000@eccles.salk.edu> Tom Bartol writes:
> : I tried 3.0-current after this merge, suspend and resume worked fine on my
> : 770 with the exception of uptime.
> 
> I can confirm that uptime, at least as reported by uptime(1), isn't
> increased in the latest -current.
> 
> Warner
> 

I confirm this as well.  Perhaps after suspend we need:

Allow ntp to update time and adjust boottime as necessary.
Then set uptime = time-boottime

Tom




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message