Date:	Wed, 26 Apr 2000 07:04:20 -0400 (EDT)
Message-Id:	<200004261104.HAA23662@indy.delorie.com>
From:	Eli Zaretskii <eliz AT delorie DOT com>
To:	sandmann AT clio DOT rice DOT edu
CC:	ams AT ludd DOT luth DOT se, djgpp-workers AT delorie DOT com
In-reply-to:	<10004251520.AA16835@clio.rice.edu> (sandmann@clio.rice.edu)
Subject:	Re: The new cwsdpmi
References:	<10004251520 DOT AA16835 AT clio DOT rice DOT edu>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
> Date: Tue, 25 Apr 2000 10:20:51 -0500 (CDT)
> 
> > Also, the "Swap disk full" message might have happened inside some
> > nested job, and when that job was aborted, CWSDPMI shrunk the swap
> > file due to the fact that some client(s) exited and freed their
> > memory.  If that's true, you won't be able to see the real size of the
> > swap file when it filled the disk.
> 
> If the swap file goes completely full, CWSDPMI prints the message and exits 
> (it doesn't expect this condition, already returned memory to the application 
> based on the fact there was free disk when the request was made, but
> something used the disk space in the meantime).

This ``something used up the disk space in the meantime'' scenario is
quite possible in the case at hand, since its TMPDIR points to the
disk (as the amount of physical RAM is very low).

Martin, if there's another disk attached to that box, you could try
pointing TMPDIR to that other disk.

FWIW, CWSDPMI r5 is working for me with no visible problems (P166,
64MB of RAM, pleanty of disk space, DOS 5.0, QEMM 8).

- Raw text -