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 >/dev/null 2>&1 Stefan -- Stefan Bethke <stb_at_lassitu.de> Fon +49 170 346 0140Received on Fri Oct 27 2006 - 14:01:17 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:01 UTC