From owner-freebsd-current  Sat Jan  4 18:13:18 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id SAA06558
          for current-outgoing; Sat, 4 Jan 1997 18:13:18 -0800 (PST)
Received: from hub.org (root@hub.org [207.107.138.200])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA06551
          for <FreeBSD-current@FreeBSD.ORG>; Sat, 4 Jan 1997 18:12:59 -0800 (PST)
Received: from localhost (scrappy@localhost) by hub.org (8.8.2/8.7.5) with SMTP id VAA22127; Sat, 4 Jan 1997 21:08:50 -0500 (EST)
Date: Sat, 4 Jan 1997 21:08:49 -0500 (EST)
From: "Marc G. Fournier" <scrappy@hub.org>
To: grog@lemis.de
cc: "John S. Dyson" <toor@dyson.iquest.net>,
        FreeBSD current users <FreeBSD-current@FreeBSD.ORG>
Subject: Re: Swap leak in -current?
In-Reply-To: <199701041632.RAA04980@freebie.lemis.de>
Message-ID: <Pine.NEB.3.95.970104210408.16960C-100000@hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 4 Jan 1997 grog@lemis.de wrote:

> John S. Dyson writes:
> >>  I've just failed a 'make world' for the second time after running out
> >>  of swap space.  I don't understand why: it looks like the make process
> >>  is using up swap at a ridiculous rate.  Here's the scenario:  Pentium
> >>  133 with 64 MB of memory, a hungry X server using about a third of
> >>  this, two swap spaces with a total of 150 MB.
> >>
> > Just updated -current kernel -- use that.  I broke it (with an optimization :-().
> 
> I included all CTM patches up to and including 2888:
> 
> FreeBSD freebie.lemis.de 3.0-CURRENT-ctm-2888 FreeBSD 3.0-CURRENT-ctm-2888 #167: Sat Jan  4 11:21:26 MET 1997     grog@freebie.lemis.de:/src/FREEBIE/sys/compile/FREEBIE  i386
> 
> The problem still occurs.  I'll try the alternative you describe in
> the other message and report.
>

	I've hit this problem with -current (will download the newest 
sources tonight and retry, as mine are from two nights ago), but hit a
second problem:

	xquake causes a panic/reboot with that kernel.  If I plug in my
old kernel (Dec 29th), xquake runs fine.

	Unfortunately, I don't seem to be geting anything in the way
of a core dump to analyze, *or* anything on the console (since am
running X, of course)...

Marc G. Fournier                                 scrappy@hub.org
Systems Administrator @ hub.org              scrappy@freebsd.org