Date: Wed, 25 Oct 2006 08:09:25 +0200 From: Andreas Klemm <andreas@freebsd.org> To: Stefan Bethke <stb@lassitu.de> Cc: current@freebsd.org Subject: Re: portupgrade not working for all ports Message-ID: <20061025060925.GA11697@titan.klemm.apsfilter.org> In-Reply-To: <CB0EB717-859B-4D1B-89F0-58549B0A3F90@lassitu.de> References: <20061023061539.GA17549@titan.klemm.apsfilter.org> <20061023212554.00062ff5@serene.no-ip.org> <CB0EB717-859B-4D1B-89F0-58549B0A3F90@lassitu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 24, 2006 at 09:12:01AM +0200, Stefan Bethke wrote: > Am 24.10.2006 um 04:25 schrieb Conrad J. Sabatier: > > >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. > > I do get this when the port uses options (or otherwise invokes dialog > (1)), and portupgrade is not on a terminal. > > On a number of machines, I update ports by a cron job, so I define - > DBATCH in pkgtools.conf for all ports. Was all interactive. Maybe at the weekend I can investigate more into this. Though it won't be the same situation as before, since I updated to -current of 2 days ago. Andreas /// -- Andreas Klemm - Powered by FreeBSD 6 Need a magic printfilter today ? -> http://www.apsfilter.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061025060925.GA11697>