Date: Thu, 25 Jan 2001 13:17:31 -0800 From: Kris Kennaway <kris@FreeBSD.ORG> To: "Geoffrey T. Falk" <gtf@cirp.org> Cc: freebsd-security@FreeBSD.ORG Subject: Re: rpc.statd bloat Message-ID: <20010125131731.A62681@citusc17.usc.edu> In-Reply-To: <200101251810.LAA04410@h-209-91-79-2.gen.cadvision.com>; from gtf@cirp.org on Thu, Jan 25, 2001 at 11:10:25AM -0700 References: <200101251726.f0PHQei65827@troutmask.apl.washington.edu> <200101251810.LAA04410@h-209-91-79-2.gen.cadvision.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 25, 2001 at 11:10:25AM -0700, Geoffrey T. Falk wrote: > In a related note: Is it normal for rpc.statd to bloat? rpc.statd on > boojum, my 4.0-RELEASE box, recently experienced a VSIZE > 274000. >=20 > This box is an NFS server, but I don't think my NFS client (NEXTSTEP=20 > 3.2) is using rpc.statd, because it runs just fine without it. Yes. It's not actually using that memory. See the archives or the FAQ for more. Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --KsGdsel6WgEHnImy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6cJfrWry0BWjoQKURAgoCAKCxVnIun0vemHTX9ZaW5ooeVUL0EgCg3U6E 7F3cB6ajZAaSVI02rIH8DSQ= =3KZb -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010125131731.A62681>