Date: Sun, 26 Nov 2000 13:22:32 -0800 (PST) From: Matt Dillon <dillon@earth.backplane.com> To: "William S. Duncanson" <caesar@starkreality.com> Cc: stable@FreeBSD.ORG Subject: Re: rpc.statd memory leak? Message-ID: <200011262122.eAQLMWN27116@earth.backplane.com> References: <5.0.0.25.2.20001125224624.00a5f7a8@maggie.netspend.net>
next in thread | previous in thread | raw e-mail | index | archive | help
:After upgrading from 4.1.1-STABLE to 4.2-STABLE, I noticed that rpc.statd
:has grown to huge proportions. Well, OK, looking at the timestamps of the
:sources, it doesn't look like rpc.statd has changed at all. It is,
:however, huge:
:root 128 0.0 0.1 263060 604 ?? Is 10:27PM 0:00.01 rpc.statd
:
:System has been rebooted within the past half hour, but look at that
:vsz. Eventually, rss will grow as well. Killing rpc.statd doesn't free
:the memory. NFS traffic on this machine is light, to say the least, with
:only one client mounting /home.
:
:Any ideas what could be causing this, or how to fix it?
Don't worry about it. rpc.statd is reserving a huge amount of VM
space for some sort of log. It has always done this. It doesn't
actually use any of it, so no real memory gets eaten. It's annoying
to look at but not actually harmful. I'm annoyed at whoever wrote it,
but I've never examined the code closely enough to figure out the best
way to 'fix' it. It has never been a priority.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011262122.eAQLMWN27116>