| 1 |
On Montag 18 Mai 2009, Mark Haney wrote: |
| 2 |
> Wil Reichert wrote: |
| 3 |
> > On Mon, May 18, 2009 at 8:26 AM, Mark Haney <mhaney@××××××××××××.org> |
| 4 |
wrote: |
| 5 |
> >> I've been extremely busy lately and have let my updates get way behind. |
| 6 |
> >> Part of that is my need to keep kde-libs-3.5 on my system for K3b, etc, |
| 7 |
> >> part of that is just too much else to do. |
| 8 |
> >> |
| 9 |
> >> The problem I've encountered is when I try to do an update while I'm |
| 10 |
> >> working, my system can slow to a crawl, on a big compile usually. I've |
| 11 |
> >> tried using nice to manage how much CPU the compile gets so I can |
| 12 |
> >> function while it's building, but it's killing the output so I can't see |
| 13 |
> >> what's going on. |
| 14 |
> >> |
| 15 |
> >> Is there another way to use nice, or to fix that problem? Or another |
| 16 |
> >> way to manage CPU usage during an emerge? |
| 17 |
> > |
| 18 |
> > I've got PORTAGE_NICENESS="15" set in my make.conf. Makes all emerges |
| 19 |
> > unnoticable on my system. |
| 20 |
> > |
| 21 |
> > Wil |
| 22 |
> |
| 23 |
> Learn something everyday. I did not know of that setting. Cool. Thanks |
| 24 |
> for the heads up. |
| 25 |
|
| 26 |
19 should be better. Once upon a time it marked portage as 'sched_batch' which |
| 27 |
was theoretically speeding up compiling. |
Archives