portupgrade not working for all ports
Andreas Klemm
andreas at freebsd.org
Wed Oct 25 06:10:21 UTC 2006
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/
More information about the freebsd-current
mailing list