From owner-freebsd-questions Sat Sep 7 09:56:57 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA18307 for questions-outgoing; Sat, 7 Sep 1996 09:56:57 -0700 (PDT) Received: from broken.whitefang.com (broken.whitefang.com [199.173.153.182]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA18292 for ; Sat, 7 Sep 1996 09:56:49 -0700 (PDT) Received: from localhost (shadows@localhost) by broken.whitefang.com (8.7.5/8.7.3) with SMTP id QAA01493 for ; Sat, 7 Sep 1996 16:55:26 +0300 (AST) X-Authentication-Warning: broken.whitefang.com: shadows owned process doing -bs Date: Sat, 7 Sep 1996 16:55:26 +0300 (AST) From: The ShadowS Know Reply-To: shadows@whitefang.com To: FreeBSD Questions List Subject: Re: /proc file system is full In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 6 Sep 1996, Yegor D. Sinelnikov wrote: > Please give me a tip how to deel with /proc filesystem when it is full. > df reports 100% and there are messages in log files regarding that > problem. It happened when I tryed to pull into vi a huge file and as a > result I had /var and /proc filled. I cleaned /var but what should I do > with /proc since it is not realy a file system. I can tell why vi totaled your /var filesystem. FreeBSD has vi.recover in /var/tmp and when you size your splices automatically in the installation program you wind up with /var bieng smaller than /usr usualy. When I was downloading the ports and packages I totaled /var/tmp/ while getting XEmacs (bloat city). So I did this, although I'm not sure if its recommended by FreeBSD gurus. $ pwd /var $ ls -al /var/tmp lrwxr-xr-x 1 root wheel 8 Sep 6 15:31 /var/tmp -> /usr/tmp $ $ df Filesystem 512-blocks Used Avail Capacity Mounted on /dev/wd0a 63550 42874 15592 73% / /dev/wd0s2f 1758174 356486 1261036 22% /usr /dev/wd0s2e 59454 2404 52294 4% /var procfs 8 8 0 100% /proc My /usr splice is much bigger so from now on everytime some program decides to write to /var/tmp, and in your care /var/tmp/vi.recover i bet it realy does it in /usr/tmp since I've made a symbolic link. I'm wondering why FreeBSD didnt decide to just put vi.recover in /usr/tmp makes more sense to me as its the bigger partition. ------------------------------------------------------------------------------- ShadowS WhiteFang Unix Software Development Thamer Al-Herbish And Consultancy. shadows@whitefang.com Specialising in Custom Network Applications for Unix Systems. -------------------------------------------------------------------------------