Setting it to invalid due the response of the developers:
https://jira.vuze.com/browse/SUP-138
** Changed in: azureus
Status: New = Invalid
** Changed in: azureus (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
Binary package hint: azureus
Limits set to 260 kilobytes per second down and 50 up. Reporting usage
in that general vicinity. Over 3 minutes, /proc/net/dev reports 325.4
kilobytes per second down, and 73.1 up. That's 25% more for down, and
46% more for up
Confirmed also in the last CVS version of vuze: 4.5.5.1_B36.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/428231
Title:
Badly under-reports bandwidth usage.
--
ubuntu-bugs mailing list
Upstream error in Jira: https://jira.vuze.com/browse/SUP-138
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/428231
Title:
Badly under-reports bandwidth usage.
--
ubuntu-bugs mailing list
I can't confirm it in a 10.10 2.6.35-24.42 i386 with vuze 4.3.0.6-1.
Have you tried to reduce the number of peers connected? It seems that
this option has a direct impact in overhead bits. And I quote from
http://wiki.vuze.com/w/Reduce_memory_usage
Many users overestimate the importance of the
I'm counting a total of 21 peers. And it should still report actual
bandwidth used with many peers.
I got bandwidth used like this (script I wrote):
wget www.chaosreigns.com/code/dl/netload.pl
chmod +x netload.pl
./netload.pl 60
dev rx mrx tx mtx dev rx mrx tx mtx dev rx mrx tx mtx
If you don't want to rely on a script I wrote, you can do:
grep eth0 /proc/net/dev | awk '{print $2}' ; sleep 60 ; grep eth0
/proc/net/dev | awk '{print $2}'
Assuming your internet connection is through your eth0 device.
/proc/net/dev includes column labels so you can verify the second column
Great script! (I'll bookmark it if you don't mind) Now I can confirm this bug:
10.10 i386 2.6.35-24.42 with vuze 4.3.0.6-1
** Changed in: azureus (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Confirmed also with last version of vuze: 4.5.1.0/4 az3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/428231
Title:
Badly under-reports bandwidth usage.
--
ubuntu-bugs mailing list
I can't add a bugwatch to the upstream error so I link it here:
http://forum.vuze.com/thread.jspa?messageID=234084
** Also affects: azureus
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, according to this report, you are not using the
most recent version of this package for your Ubuntu release. Please
upgrade to the most recent version and let us know if you are still
having this issue.
Another random switch to invalid without testing, huh (bug #434979)?
The version was current when the bug was reported, and the problem
continues to exist.
$ lsb_release -rd
Description:Ubuntu 10.10
Release:10.10
$ apt-cache policy azureus
azureus:
Installed: 4.3.0.6-1
** Changed
Hi Darxus,
Neither the bug #434979 nor this one were random changes. I couldn't
confirm it in my 10.04 with the system monitor so I asked and I changed
to Incomplete and I thinks that's the right thing to do. Except that I
should have written in my comment that I didn't see this issue in recent
Yup, sorry, I forgot to verify that the status had been confirmed.
** Changed in: azureus (Ubuntu)
Status: Confirmed = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/428231
Title:
Badly
14 matches
Mail list logo
