From owner-freebsd-stable Sun Oct 15 22:52: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from code.omcl.org (code.cs.unm.edu [64.106.46.110]) by hub.freebsd.org (Postfix) with ESMTP id 5384B37B66D for ; Sun, 15 Oct 2000 22:52:04 -0700 (PDT) Received: from code.omcl.org (localhost [127.0.0.1]) by code.omcl.org (8.11.1/8.11.1) with ESMTP id e9G5q1Q98267; Sun, 15 Oct 2000 23:52:01 -0600 (MDT) (envelope-from spcoltri@code.omcl.org) Message-Id: <200010160552.e9G5q1Q98267@code.omcl.org> To: "Wyness Casama" Cc: stable@freebsd.org Subject: Re: procfs: out of memory! In-Reply-To: Your message of "Sun, 15 Oct 2000 22:49:19 PDT." Date: Sun, 15 Oct 2000 23:52:01 -0600 From: Steve Coltrin Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>I'm having a little trouble with my procfs... actually, it seems it's a >>>little too small (4k) for what I'm doing. Is it possible to resize the >>>procfs to say: 1mb+? >>procfs isn't an ordinary file system; it's a projection of system memory >into >>the file system hierarchy. You never actually put files in it. >Thanks for the info. :) I was thinking about the size of procfs (4k) I'm >trying to increase that memory space cause the procfs is always full... procfs _isn't a real file system_. The results of "df /proc" are meaningless. >I'm >not too sure why, but it's preventimg me from even running 'top' or >anything. The problem is certainly something else, probably... >the symptoms just seem to have started as soon as I installed a 3com 3905B >10/100 NIC. ...that. Try recompiling top, ps, and the various other programs that look at kernel memory; the layout of kernel data structures is compiled into them and changing kernel configuration tends to discombobulate them. >Any ideas on how I could alleviate this problem? would it be safe to simply >try to remove the files in there? I don't think you can remove the entries in /proc; if you could, it would not be a very good idea :) > --wgc -spc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message