Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 4 Apr 2003 12:25:33 +0200
From:      CARTER Anthony <a.carter@cordis.lu>
To:        Matt <matt@xtaz.co.uk>, CARTER Anthony <a.carter@cordis.lu>, freebsd-current@freebsd.org
Subject:   Re: OOOPS - portupgrade/Swapfile/???
Message-ID:  <200304041225.33721.a.carter@intrasoft.lu>
In-Reply-To: <20030404100459.M67134@xtaz.co.uk>
References:  <200304041156.38051.a.carter@intrasoft.lu> <20030404100459.M67134@xtaz.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
Did portupgrade get updated then?

I am not using gnome...

The only thing I can think of is that an update has created a loop within 
itself, thereby launching subsequent sorts...I get 10 or so sorts, about 
20-30 make's, kill them they come back...

Anthony

On Friday 04 April 2003 12:09, Matt wrote:
> On Fri, 4 Apr 2003 11:56:37 +0200, CARTER Anthony wrote
>
> > Watching with swapinfo, my 500Mb (256 Mb Ram) swapfile just fills
> > up...on stopping portupgrade, swap file is emptied...
>
> I have exactly the same thing, just my machine can cope with it a bit
> better as I have 512M physical and 1gig swap. It's currently running a
> portupgrade -rai and doing all the recent gnome commits. The first 6 or 7
> upgrades of installed ports went without a hitch but since then at the
> points where it says "Building ...." and "Registering installation for
> ...." I get this:
>
> OK? [yes]
> --->  Build of x11/gnomesession started at: Fri, 04 Apr 2003 11:04:52 +0100
> --->  Building '/usr/ports/x11/gnomesession'
> make: Max recursion level (500) exceeded.: Resource temporarily unavailable
>
> and the physical ram in use just goes up and up and up until it runs out
> and then the swap space does the same. After a few minutes (luckily before
> it runs out) it stops. All the ram is free'd and the portupgrade carries
> on.
>
> During this time looking at a "top" it appears it's due to around ten
> "sort" processes doing something or other at the time.
>
> This looks more like a portupgrade issue rather than a -CURRENT issue
> however.
>
> Matt.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200304041225.33721.a.carter>