Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 162091 - Feature Request: Maximum download rate
Summary: Feature Request: Maximum download rate
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-06-29 19:59 UTC by Sigge Kotliar
Modified: 2014-01-21 22:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-06-29 20:02:50 UTC


Attachments (Terms of Use)

Description Sigge Kotliar 2005-06-29 19:59:12 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; sv-SE; rv:1.7.8) Gecko/20050623 Fedora/1.0.4-5 Firefox/1.0.4

Description of problem:
Something that I feel would make yum a much better tools is the ability to limit the maximum download rate.
As it is now, yum uses all available bandwidth, making web surfing or doing other things rather slow while downloading, which can take a while when updating openoffice, eclipse etc.

Would it be very difficult to implement a maximum download rate setting like:

yum --maxdownloadrate=40 
(kB/s or something)

I think this would be a great feature for users of slow broadband connections, or modems. People would no longer have to "plan" their updates, but just run them in the background

Version-Release number of selected component (if applicable):


How reproducible:
Didn't try

Steps to Reproduce:


Additional info:

Comment 1 Seth Vidal 2005-06-29 20:02:50 UTC
look at the 'bandwidth' option in the yum.conf man page.


Note You need to log in before you can comment on or make changes to this bug.