| 1 |
Sorry...replying to myself...any how... |
| 2 |
|
| 3 |
Yes, I had been seeing it for a while, primarily over SSH. Why it fixed itself? I don't know, but I would guess the portage cache regen on the nightly had something to do with it too. Any how...hopefully it's fixed...but I would guess it'll happen again, so I'll test out more when it does! |
| 4 |
|
| 5 |
Ben |
| 6 |
|
| 7 |
|
| 8 |
|
| 9 |
----- Original Message ---- |
| 10 |
From: BRM <bm_witness@×××××.com> |
| 11 |
To: gentoo-user@l.g.o |
| 12 |
Sent: Friday, September 19, 2008 10:32:30 PM |
| 13 |
Subject: Re: [gentoo-user] Emerge takes a long time calculating dependencies... |
| 14 |
|
| 15 |
Well...I got to trying the methods out tonight...and first started with a 'time' of my standard procedure... |
| 16 |
|
| 17 |
$ time emerge world -vuDNp |
| 18 |
real 1m41.658s |
| 19 |
user 1m8.664s |
| 20 |
sys 0m16.921s |
| 21 |
|
| 22 |
$ time emerge world -vuDNp |
| 23 |
real 0m36.697s |
| 24 |
user 0m35.026s |
| 25 |
sys 0m1.124s |
| 26 |
|
| 27 |
|
| 28 |
That was two runs right in a row...but no where near the time level I saw the other day - which was well over half an hour. (I went to bed before it stopped the other day...) |
| 29 |
|
| 30 |
I am going to guess that it was a portage cache issue and the daily update fixed it, or something. |
| 31 |
|
| 32 |
Any how...will keep the ideas in mind should it happen again. |
| 33 |
|
| 34 |
Thanks All! |
| 35 |
|
| 36 |
Ben |
| 37 |
|
| 38 |
|
| 39 |
----- Original Message ---- |
| 40 |
From: Daniel Pielmeier <daniel.pielmeier@××××××××××.com> |
| 41 |
To: gentoo-user@l.g.o |
| 42 |
Sent: Thursday, September 18, 2008 10:04:11 AM |
| 43 |
Subject: Re: [gentoo-user] Emerge takes a long time calculating dependencies... |
| 44 |
|
| 45 |
2008/9/18 BRM <bm_witness@×××××.com>: |
| 46 |
|
| 47 |
> And I am only referring to the time specified in the "calculating dependencies" stage when one first runs "emerge world -vuDNp". |
| 48 |
|
| 49 |
Is the second run significantly faster, if yes chances are high that |
| 50 |
there is a problem with the portage cache. |
Archives