nice configure

[William Davis]

On Jan 8, 2009, at 10:54 PM, Ryan Schmidt wrote:

> If you set "buildnicevalue" in ${prefix}/etc/macports/macports.conf,  
> MacPorts runs the build phase through the "nice" command so that  
> "port" runs at a lower priority and doesn't steal cycles from other  
> processor-intensive tasks you might have running.
>
> Would there be any advantage (or rather any disadvantage) to making  
> the other phases, in particular the configure phase, nice as well?
>
>
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

AFAIK the nice command has been broken for a very long time.  Just  
bring up Activity Monitor and check it out.  You will fine the %CPU  
used by "nice" processes is always zero (unless you are using a really  
old OS).

William Davis
frstanATbellsouthDOTnet
Mac OS X.5.6 Darwin 9.5.0
XQuartz 2.3.2 (xorg-server 1.4.2-apple31)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non