From owner-freebsd-current Tue May 11 15: 9:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id AACAA15250 for ; Tue, 11 May 1999 15:09:40 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id RAA18123 for current@freebsd.org; Tue, 11 May 1999 17:09:38 -0500 (CDT) From: Kevin Day Message-Id: <199905112209.RAA18123@home.dragondata.com> Subject: Incorrect memory sizes reported To: current@freebsd.org Date: Tue, 11 May 1999 17:09:36 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not sure if this is related to the bug I found in 3.1, regarding mmaping devices, then forking, but with my -current NFS server: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 139 root 2 0 257M 452K select 0:00 0.00% 0.00% rpc.statd 257M? :) ps shows similar info... Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message