Date: Tue, 26 Oct 2010 15:23:54 +0200 From: Erik Trulsson <ertr1013@student.uu.se> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: rpcbind, rpc.statd memory footprint Message-ID: <20101026132354.GA79188@owl.midgard.homeip.net> In-Reply-To: <ia6jrk$8bb$1@dough.gmane.org> References: <ia6jrk$8bb$1@dough.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 26, 2010 at 03:08:06PM +0200, Ivan Voras wrote: > I'm not sure what to expect from these (i.e. what is "normal" in this > case?) but the VM sizes for the NFS-used rpc.statd and rpcbind here look > a bit too big, compared to their resident sizes: > > 778 root 1 44 0 26420K 3256K select 1 0:01 0.00% > rpcbind > 891 root 1 44 0 263M 1296K select 1 0:01 0.00% > rpc.statd > > This is 8-stable amd64. Could there be a memory leak somewhere, > especially in rpc.statd? FAQ: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#STATD-MEM-LEAK (Short version: That is expected behaviour from rpc.statd) -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101026132354.GA79188>