From owner-freebsd-current Mon Jan 11 09:54:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04712 for freebsd-current-outgoing; Mon, 11 Jan 1999 09:54:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04706 for ; Mon, 11 Jan 1999 09:54:14 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id JAA96433; Mon, 11 Jan 1999 09:53:33 -0800 (PST) (envelope-from dillon) Date: Mon, 11 Jan 1999 09:53:33 -0800 (PST) From: Matthew Dillon Message-Id: <199901111753.JAA96433@apollo.backplane.com> To: Konstantin Chuguev Cc: freebsd-current@FreeBSD.ORG Subject: Re: rpc.statd eats 257M on 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi. : :I'm not sure, is it a bug or a feature? :.. :.................... : 147 root 2 0 257M 256K select 0:00 0.00% 0.00% rpc.statd : ^^^ !!! ^^^^^ RSS is reasonable It's because rpc.statd does this: /* File now open. mmap() it, with a generous size to allow for */ /* later growth, where we will extend the file but not re-map it. */ status_info = (FileLayout *) mmap(NULL, 0x10000000, PROT_READ | PROT_WRITE, MAP_SHARED, status_fd, 0); It's stupid code, but the process doesn't actually eat any resources so I wouldn't worry about it. It is an eyesore, though :-( -Matt :What do kernel gurus think about this? : :-- : Konstantin V. Chuguev. System administrator of Southern Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message