1 |
The answer to supplying custom arguments to portage's download command is |
2 |
exactly where it should be - in a man page. |
3 |
|
4 |
equery files portage |
5 |
|
6 |
will list them, it's in section 5 |
7 |
|
8 |
On 06 Jan 2010 8:38 PM, "Ricardo Saffi Marques" <saffi@××××××××××××××.br> |
9 |
wrote: |
10 |
|
11 |
Is there any way I can configure (pass arguments to) emerge's "wget" (used |
12 |
for fetching) to limit it's rate to a certain amount |
13 |
of KB/s? |
14 |
|
15 |
I don't want to make a global/system-wide change, just for portage. |
16 |
|
17 |
I did find a way to limit the bandwidth while syncing. All I had to do was |
18 |
to put this on my /etc/make.conf: |
19 |
|
20 |
PORTAGE_RSYNC_EXTRA_OPTS="--partial --progress --delete-after |
21 |
--human-readable --bwlimit=50" |
22 |
|
23 |
(for instance). |
24 |
|
25 |
I do know there is parameter for wget, which is "--limitrate". Any way I |
26 |
could set this inside portage? |
27 |
|
28 |
Regards, |
29 |
|
30 |
Saffi |
31 |
|
32 |
-- |
33 |
Ricardo Saffi Marques |
34 |
http://www.las.ic.unicamp.br/~saffi/ |
35 |
====================================================== |
36 |
Laboratory of System Administration and Security - LAS |
37 |
Institute of Computing - IC |
38 |
P.O. Box: 6176 |
39 |
University of Campinas - UNICAMP |
40 |
13083-852, Campinas, SP, Brazil |
41 |
====================================================== |