From owner-freebsd-stable Sun Jan 28 16:46: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from giroc.albury.net.au (giroc.albury.NET.AU [203.15.244.13]) by hub.freebsd.org (Postfix) with ESMTP id 625B637B400 for ; Sun, 28 Jan 2001 16:45:40 -0800 (PST) Received: (from nicks@localhost) by giroc.albury.net.au (8.11.1/8.11.1) id f0T0jSI32262; Mon, 29 Jan 2001 11:45:28 +1100 (EST) Date: Mon, 29 Jan 2001 11:45:28 +1100 From: Nick Slager To: Bill Moran Cc: stable@FreeBSD.ORG Subject: Re: rpc.statd mem leak? Message-ID: <20010129114528.A21749@albury.net.au> References: <3A74B023.1E2D4D4A@mail.iowna.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A74B023.1E2D4D4A@mail.iowna.com>; from wmoran@mail.iowna.com on Sun, Jan 28, 2001 at 06:49:55PM -0500 X-Homer: Whoohooooooo! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Bill Moran (wmoran@mail.iowna.com): > I seem to be "memory leak guy" this month ... > > Is it normal for rpc.statd to soak up 257M (as reported by top in the > size column)? The "res" column shows 542K. > The machine seems to be functioning just fine otherwise. It just seems a > little unusual. > It's a 4.2-STABLE (Jan 8) machine and it's servicing 2 NFS connections > as well as running samba and netatalk. Not much else going on other than > Vinum mirrored drives and nightly backups using dump. Search the mail archives; basically it's reserving a heap of VM space but not actually using it. It's not harmful. Nick -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message