Bug 77932 - could have a bandwidth limiter built into the file copy dialogue when copying over fish?
Summary: could have a bandwidth limiter built into the file copy dialogue when copying...
Status: RESOLVED DUPLICATE of bug 27212
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: fish (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Jörg Walter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-18 18:18 UTC by Daniel Quinn
Modified: 2006-11-04 22:02 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Quinn 2004-03-18 18:18:46 UTC
Version:           unknown (using KDE 3.2.1, Gentoo)
Compiler:          gcc version 3.3.3 20040217 (Gentoo Linux 3.3.3, propolice-3.3-7)
OS:          Linux (i686) release 2.4.25

i'm copying about 1gb of stuff from my home computer to my work box and there's no way to limit the download speed on this end.  see, copying all this stuff from  work means that i'm hogging all the pipe on my home box's tiny pipe and any sites etc served from there will no be heavily bogged down.  if i was using scp, i'd just include the "-l" switch and limit the bandwidth for the transfer, but using konqueror, i don't have this option.

some sort of slider would be really nifty, but something as simple as a text box like:

  limit transfer to [ ___ ] k/sec

would work just as well.
Comment 1 Thomas Otto 2004-07-25 15:56:01 UTC
I would second respectively even extend that and ask for a general limiting facitily even for normal file copy operations (when its on nfs e.g.), plus http/ftp/fish and all the other kio data transfers. I.e. implement this on a lower level than just fish.

The GUI option itself might be in the data transfer box or maybe some general option for that.

(..and daniel as for userside bandwidth shaping have a look at trickle.)
Comment 2 madman 2006-03-25 17:23:43 UTC
Seems to be similar to bug 27212, maybe set it as a duplicate of that bug?
Comment 3 Martin Koller 2006-11-04 22:02:54 UTC

*** This bug has been marked as a duplicate of 27212 ***