From owner-freebsd-current Mon Jun 1 19:16:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10951 for freebsd-current-outgoing; Mon, 1 Jun 1998 19:16:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10884 for ; Mon, 1 Jun 1998 19:15:49 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id VAA01572; Mon, 1 Jun 1998 21:15:38 -0500 (EST) (envelope-from toor) Message-Id: <199806020215.VAA01572@dyson.iquest.net> Subject: Re: VSZ of rcp.statd ?? In-Reply-To: <199806020133.AA02102@mozart> from "John W. DeBoskey" at "Jun 1, 98 09:33:43 pm" To: jwd@unx.sas.com (John W. DeBoskey) Date: Mon, 1 Jun 1998 21:15:38 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John W. DeBoskey said: > Hi, > > The rpc.statd process seems to be (ahem), very large on my machines. The > two sample below are from a just rebooted machine, and one that's been up > for 13 days. The same is true for machines with uptimes of 50 days. > > I'm thinking this is normal, since I'm accessing 30,000 files from my > fileserver during a build process. However, I'd like to know what other > people think, and if it's 'normal'. > > Comments? Critiques? > It is big because of a mmap of /var/db/statd.status, and 0x10000000 is allocated to the mapping. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message