From owner-freebsd-current@FreeBSD.ORG Fri Oct 27 16:01:17 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 C6F1B16A589 for ; Fri, 27 Oct 2006 16:01:17 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FD9D43D53 for ; Fri, 27 Oct 2006 16:01:15 +0000 (GMT) (envelope-from stb@lassitu.de) Received: (from stb@koef.zs64.net) (authenticated) by koef.zs64.net (8.13.8/8.13.8) with ESMTP id k9RG1Alr079548 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 27 Oct 2006 18:01:11 +0200 (CEST) (envelope-from stb@lassitu.de) In-Reply-To: <20061027143447.GN20405@obiwan.tataz.chchile.org> References: <20061023061539.GA17549@titan.klemm.apsfilter.org> <20061023212554.00062ff5@serene.no-ip.org> <20061027143447.GN20405@obiwan.tataz.chchile.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Fri, 27 Oct 2006 18:02:34 +0200 To: Jeremie Le Hen X-Mailer: Apple Mail (2.752.2) Cc: "Conrad J. Sabatier" , 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 16:01:17 -0000 Am 27.10.2006 um 16:34 schrieb Jeremie Le Hen: > 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. Dialog doesn't like not talking to a tty. Just try $ dialog --yesno "foo" 6 20 yes /dev/null 2>&1 Stefan -- Stefan Bethke Fon +49 170 346 0140