From owner-freebsd-stable  Sun Jan 28 15:53:49 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from clmboh1-smtp3.columbus.rr.com (unknown [65.24.0.112])
	by hub.freebsd.org (Postfix) with ESMTP id 9086D37B404
	for <stable@freebsd.org>; Sun, 28 Jan 2001 15:53:32 -0800 (PST)
Received: from mail.iowna.com (dhcp065-024-023-038.columbus.rr.com [65.24.23.38])
	by clmboh1-smtp3.columbus.rr.com (8.11.2/8.11.2) with ESMTP id f0SNp9r03330
	for <stable@freebsd.org>; Sun, 28 Jan 2001 18:51:10 -0500 (EST)
Message-ID: <3A74B023.1E2D4D4A@mail.iowna.com>
Date: Sun, 28 Jan 2001 18:49:55 -0500
From: Bill Moran <wmoran@mail.iowna.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: stable@freebsd.org
Subject: rpc.statd mem leak?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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.

-Bill


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message