From xemacs-m  Fri Jan 17 07:47:07 1997
Received: from alphatech.com ([198.112.236.2])
          by xemacs.org (8.8.4/8.8.4) with SMTP
	  id HAA02377 for <xemacs-beta@xemacs.org>; Fri, 17 Jan 1997 07:47:02 -0600 (CST)
Received: from venus.alphatech.com by alphatech.com (4.1/SMI-4.1)
	id AA24753; Fri, 17 Jan 97 08:41:38 EST
Received: from pochacco.alphatech.com by venus.alphatech.com (4.1/SMI-4.1)
	id AA19306; Fri, 17 Jan 97 08:48:48 EST
Received: by pochacco.alphatech.com (SMI-8.6/SMI-SVR4)
	id IAA01841; Fri, 17 Jan 1997 08:40:52 -0500
Sender: greg@pochacco.alphatech.com
To: drich@cisco.com
Cc: XEmacs Beta List <xemacs-beta@xemacs.org>
Subject: Re: Build report on Solaris, and vfork problem
References: <199701170114.RAA03994@sandman>
From: greg@alphatech.com (Greg Klanderman)
Date: 17 Jan 1997 08:40:51 -0500
In-Reply-To: Dan Rich's message of Thu, 16 Jan 1997 17:14:35 -0800
Message-Id: <ug915sctcs.fsf@pochacco.alphatech.com>
Lines: 26
X-Mailer: Gnus v5.2.40/XEmacs 19.15


>>>>> "Dan" == Dan Rich <drich@cisco.com> writes:
Dan> 
Dan> I have finally gotten my Solaris system up and running, so here is my
Dan> first build report.
Dan> 
Dan> I have one problem, I am receiving the error:
Dan> 	Doing vfork: not enough space
Dan> quite often when running external processes (such as movemail and
Dan> pgp).  Has anyone else seen this, and do you know of a solution?  I
Dan> don't appear to be out of swap space (although I could use a little more):

I used to get that all the time in 19.13.  It was due to insufficient swap space
but could also be caused by bumping up against a system or per user process
limit.  Doubling my swap space cured this.

Dan>     drich@sandman|615> swap -l 
Dan>     swapfile             dev  swaplo blocks   free
Dan>     /dev/dsk/c0t0d0s1   32,1      16 132224    256
Dan>     drich@sandman|616> swap -s
Dan>     total: 73008k bytes allocated + 14352k reserved = 87360k used, 24560k available

24 Mb avail swap looks too low if I recall correctly.  How big is your XEmacs
process?

Greg

