Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Oct 2006 16:34:48 +0200
From:      Jeremie Le Hen <jeremie@le-hen.org>
To:        "Conrad J. Sabatier" <conrads@cox.net>
Cc:        current@freebsd.org
Subject:   Re: portupgrade not working for all ports
Message-ID:  <20061027143447.GN20405@obiwan.tataz.chchile.org>
In-Reply-To: <20061023212554.00062ff5@serene.no-ip.org>
References:  <20061023061539.GA17549@titan.klemm.apsfilter.org> <20061023212554.00062ff5@serene.no-ip.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

On Mon, Oct 23, 2006 at 09:25:54PM -0500, Conrad J. Sabatier wrote:
> Not sure what's causing this, but I'm seeing the "script" child
> processes spawned by portupgrade consuming an inordinate amount of CPU,
> as much as 80+%.  This does make the configure stage appear to hang
> interminably much of the time.
> 
> This is under 7.0-CURRENT/amd64 with both portupgrade and
> portupgrade-devel.  It's gotten so bad, in fact, that I find myself
> more and more resorting to manually upgrading ports, which works fine
> and does not hog CPU at all.

I caught such a behaviour as well on my -CURRENT from Oct 21
(with SSP patch applied).  I saw once script(1) eating most of
the CPU and another time, this was dialog(1).  I was running
portupgrade -af with some MAKE_ARGS in pkgtools.conf.
I haven't taken time to inverstigate, though.

Regards,
-- 
Jeremie Le Hen
< jeremie at le-hen dot org >< ttz at chchile dot org >



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