From owner-freebsd-questions Thu Feb 25 10:11: 2 1999 Delivered-To: freebsd-questions@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 9D9E014E35 for ; Thu, 25 Feb 1999 10:10:55 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id MAA25825; Thu, 25 Feb 1999 12:10:31 -0600 (CST) Date: Thu, 25 Feb 1999 12:10:31 -0600 From: Dan Nelson To: Mike Knoll Cc: questions@FreeBSD.ORG Subject: Re: Impossible memory size reporting Message-ID: <19990225121031.B25529@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from "Mike Knoll" on Thu Feb 25 12:26:14 GMT 1999 X-OS: FreeBSD 3.1-STABLE Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Feb 25), Mike Knoll said: > I have rpc.statd running on a 3.1-RELEASE machine, and it shows a > virtual size of 263megs. Is something wrong in my configuration? > Everything works fine, but this is an insane amount of memory to be > resonable. > > My 2.2.8-RELEASE machine does not do this. > > ps -axl > 0 7316 1 0 2 0 262968 552 select Is ?? 0:00.00 rpc.statd I think I remember reading about this a while back, and the culprit is the mmap() that rpc.statd does. It definitely does not use that much memory. A ps on a 2.2.8 prints reasonable numbers. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message