Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!sgi!mips!public!thad
From: thad@public.BTR.COM (Thaddeus P. Floryan)
Newsgroups: comp.sys.3b1
Subject: Re: Virtual memory and exhaustion
Keywords: virtual-memory exhaustion poop
Message-ID: <3224@public.BTR.COM>
Date: 27 Jun 91 12:13:01 GMT
References: <137@morwyn.UUCP>
Organization: BTR Public Access UNIX, Mountain View CA
Lines: 38

In article <137@morwyn.UUCP> forrie@morwyn.UUCP (Forrie Aldrich) writes:
| I've been noticing this problem more and more recently as I attempt
| to compile things.  And the problem is consistently saying :
| 
| 	"Virtual Memory exhausted ..."
| 
| Now, I don't understand why others with nearly the SAME configuration
| would NOT have this problem and I do (or is it just my luck?).
| 
| My configuration is as follows:
| 
| 	3.51m kernel
| 	3.51 development set
| 	2 meg RAM
| 	67 meg hard-disk
| [...]

So, how much swap space do you have allocated and how many other (large)
processes are "running"?

To determine the swap space allocated on your hard drive, do the following
and be SURE to type a lower-case "T" and not an "I":

	$ su
	# iv -t /dev/rfp000

If the size of partition 1 is 4000 or 5000, you're running the "default"
which simply may not be enough for what you do on your system.  If you have
a large HD, a swap partition size of 8000, 10000 or 12000 may be in order.

To check what other processes are running, issue a "ps -ef" command.

You can also use the "mapmem" program to dynamically track the actual space
used/free in RAM and in the swap partition.  I presume "mapmem" is archived
at osu-cis; I got my copy when it was posted to the unix-pc.sources and to
the comp.sys.att newsgroups on 29-April-1990.

Thad Floryan [ thad@btr.com (OR) {decwrl, mips, fernwood}!btr!thad ]