From owner-freebsd-current Tue May 11 22:40:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from mx.nsu.ru (mx.nsu.ru [193.124.215.71]) by hub.freebsd.org (Postfix) with ESMTP id 5261814F20 for ; Tue, 11 May 1999 22:38:48 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from iclub.nsu.ru (fjoe@iclub.nsu.ru [193.124.222.66]) by mx.nsu.ru (8.9.1/8.9.0) with ESMTP id MAA14146; Wed, 12 May 1999 12:35:51 +0700 (NOVST) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.8.5) with ESMTP id MAA15772; Wed, 12 May 1999 12:35:38 +0700 (NSS) Date: Wed, 12 May 1999 12:35:38 +0700 (NSS) From: Max Khon To: Kevin Day Cc: current@FreeBSD.ORG Subject: Re: Incorrect memory sizes reported In-Reply-To: <199905112209.RAA18123@home.dragondata.com> 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 hi, there! On Tue, 11 May 1999, Kevin Day wrote: > 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... got the same on -stable machine (built 28 Apr) about a week ago /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message