From owner-freebsd-stable Sat Nov 25 21: 3:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fire.starkreality.com (fire.starkreality.com [198.78.158.210]) by hub.freebsd.org (Postfix) with ESMTP id 390FF37B479 for ; Sat, 25 Nov 2000 21:03:15 -0800 (PST) Received: from famine.starkreality.com (fourhorsemen.starkreality.com [198.78.158.218]) by fire.starkreality.com (8.11.1/8.11.1) with ESMTP id eAQ53Ai05193 for ; Sat, 25 Nov 2000 23:03:12 -0600 (CST) Message-Id: <5.0.0.25.2.20001125224624.00a5f7a8@maggie.netspend.net> X-Sender: caesar@mail.starkreality.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 25 Nov 2000 23:03:10 -0600 To: stable@freebsd.org From: "William S. Duncanson" Subject: rpc.statd memory leak? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message