From owner-freebsd-current@FreeBSD.ORG Fri Oct 27 14:34:14 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E20216A412; Fri, 27 Oct 2006 14:34:14 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EDFC43D5C; Fri, 27 Oct 2006 14:34:08 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp1-g19.free.fr (Postfix) with ESMTP id 13002345F; Fri, 27 Oct 2006 16:34:08 +0200 (CEST) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 40F4F9E6C2; Fri, 27 Oct 2006 14:34:48 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 12FB5405B; Fri, 27 Oct 2006 16:34:48 +0200 (CEST) Date: Fri, 27 Oct 2006 16:34:48 +0200 From: Jeremie Le Hen To: "Conrad J. Sabatier" Message-ID: <20061027143447.GN20405@obiwan.tataz.chchile.org> References: <20061023061539.GA17549@titan.klemm.apsfilter.org> <20061023212554.00062ff5@serene.no-ip.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061023212554.00062ff5@serene.no-ip.org> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: current@freebsd.org Subject: Re: portupgrade not working for all ports X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 14:34:14 -0000 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 >