From owner-freebsd-questions Sun Dec 12 7:28:55 1999 Delivered-To: freebsd-questions@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id ACE3D14D11 for ; Sun, 12 Dec 1999 07:28:52 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id QAA20235; Sun, 12 Dec 1999 16:28:51 +0100 (CET) (envelope-from olli) Date: Sun, 12 Dec 1999 16:28:51 +0100 (CET) From: Oliver Fromme Message-Id: <199912121528.QAA20235@dorifer.heim3.tu-clausthal.de> To: cjclark@home.com Subject: Re: bloated rpc.statd Cc: freebsd-questions@freebsd.org Newsgroups: list.freebsd-questions Organization: Administration TU Clausthal Reply-To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (posted and mailed) Crist J. Clark wrote in list.freebsd-questions: > Marc Schneiders wrote, > > On Tue, 7 Dec 1999, Stephen Roome wrote: > > > > > rpc.statd appears to get quite large, does anyone else have this, or is it some > > > curious problem only I get ? > > > [...] > > > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > > > root 41712 0.0 0.0 262976 8 ?? Is 30Nov99 0:00.00 rpc.statd > > > > I have this occasionally, also 256 MB, which happens to be the real > > memory of my box. It does not come back immediately though. I would be > > interested in an explanation. > > The obligatory "Me too!!" post. > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 68532 root 2 0 257M 0K select 0:00 0.00% 0.00% > > It's supposedly using 257 MB on a system with 24 MB RAM and 80 MB of No, it is not. This is really a FAQ and should be in the FAQ. The VSZ column in ps (SIZE column in top) specifies the _virtual_ size of the process. This is _not_ the amount of memory that the process is actually using. rpc.rstatd allocates 256 Mbyte of memory, but only uses some small pieces of it. The rest does not take up any system resources, so there's no reason to be worried. FreeBSD (and many other operating systems) implement a memory allocation scheme called "memory overcommit". This means that a process can allocate as much memory as it wants, but it does not occupy any real memory (neither physical RAM nor swap), until the process actually uses the memory. It's not a bug, it's a feature! :) Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message