Date: Thu, 25 Jan 2001 11:05:56 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: "Geoffrey T. Falk" <gtf@cirp.org> Cc: freebsd-security@FreeBSD.ORG Subject: Re: rpc.statd bloat Message-ID: <20010125110556.B23406@Odin.AC.HMC.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
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. > > This box is an NFS server, but I don't think my NFS client (NEXTSTEP > 3.2) is using rpc.statd, because it runs just fine without it. It's not actually consuming any where near that much memory (or at least it shouldn't be). The problem is that it mmaps 256MB of a status file in /var so it can extend the file as needed without having to re-mmap it each time. This looks strange, but really only wastes a bit of address space in the process so it's pretty harmless. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. 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?20010125110556.B23406>