*BSD News Article 9872


Return to BSD News archive

Received: by minnie.vk1xwt.ampr.org with NNTP
	id AA6695 ; Tue, 12 Jan 93 07:04:15 EST
Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!sdd.hp.com!nobody
From: mattb@sdd.hp.com (Matt Bonner)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Solved: Virtual Memory Exhausted
Date: 14 Jan 1993 18:52:02 GMT
Organization: Hewlett-Packard, San Diego Division
Lines: 29
Distribution: world
Message-ID: <1j4coiINN937@hpsdlss3.sdd.hp.com>
NNTP-Posting-Host: hpsdlg16.sdd.hp.com
Keywords: virtual memory, swap, limit

Well, someone finally offered the golden hint that solved all
my problems.  I posted a while ago asking how to fix virtual
memory exhausted" errors I was getting during compiles,  and
received all sorts of help setting up swap space with disklabel
and /etc/fstab from serini@dsi.unimi.it (Thanks Piero!).  

But after finally getting that configured, the problem remained.  
kym@bingsuns.cc.binghamton.edu (R. Kym Horsell) suggested I get 
gcc 2.2.x from ref.tfs.com, which solved many of the problems, 
but not all.  Finally yesterday, a post from karl@NeoSoft.com 
(Karl Lehenbauer) tipped me off to the limit/ulimit shell 
commands (for csh/bash, respectively).  After raising the datasize 
limit (in csh), I was able to compile everything and run xbench 
to completion.  (Amancio, I will send you my results soon.)

Thank you all for all your help!  In return, if anyone else is 
having problems, feel free to mail me instead of bothering all 
these kind souls further.  (Hope I don't get flooded now!)

NOTE: I am not claiming to be an expert; I'm nowhere close. But
maybe I can help people avoid muddling through it as badly as I 
did.

Cheers,
Matt
-- 
Matt Bonner                  |  Email: mattb@sdd.hp.com
Hewlett-Packard Company      |  Snail: 16399 West Bernardo Drive
Ink-jet Components Division  |         San Diego, CA  92127-1899