| 1 |
On Mon, 13 Jul 2020 11:50:08 -0500, Matt Connell (Gmail) wrote: |
| 2 |
|
| 3 |
> > You have to consider the --jobs option passed to emerge at the same |
| 4 |
> > time. It's no use limiting each emerge to 2 processes if you then run |
| 5 |
> > multiple emerges in parallel. |
| 6 |
> |
| 7 |
> According to the man page, this defaults to 1 if emerging |
| 8 |
> interactively, which I always do. |
| 9 |
|
| 10 |
It does, but that's a very inefficient use of resources as a single emerge |
| 11 |
often spends a lot of its time not hammering the CPU. |
| 12 |
|
| 13 |
|
| 14 |
-- |
| 15 |
Neil Bothwick |
| 16 |
|
| 17 |
"Bad dog! Leave that wire alone.....click.....###@*##....NO TERRIER |
Archives