| 1 |
Grant Edwards wrote: |
| 2 |
> Now that the public key stuff is working again (knock on wood), I'm |
| 3 |
> curious if it's usual for an emerge --sync to take 10-15 minutes |
| 4 |
> longer than it used due to the "Verifying /usr/portage" step. |
| 5 |
> |
| 6 |
> On some systems (with fewer packages installed) it only takes a minute |
| 7 |
> or less. But, on my "main" desktop system it takes 10-15 minutes every |
| 8 |
> time. During the verify step, the emerge process is only using about |
| 9 |
> 5% of the CPU, and my system is running 80% or more idle. |
| 10 |
> |
| 11 |
|
| 12 |
|
| 13 |
I haven't timed mine yet but that sounds about like mine here. I'm not |
| 14 |
sure what the bottleneck is but I have a four core AMD CPU running at |
| 15 |
3.2GHz with 16GBs of ram and SATA spinning rust drives. While I'm glad |
| 16 |
to have the added security measures, it does add a significant amount of |
| 17 |
time to the update process, the tree not the compile part. We all know |
| 18 |
the compile part can get big. lol |
| 19 |
|
| 20 |
I guess like everything else, we'll just have to get used to it. People |
| 21 |
will hack a ham sandwich if they can and can get something from it. |
| 22 |
That would be mustard on mine. Some may like Mayo, which is fine too. |
| 23 |
;-) |
| 24 |
|
| 25 |
Dale |
| 26 |
|
| 27 |
:-) :-) |
Archives