![]() Registered Member ![]()
|
These were sent to me by the admin of a private tracker -
Yes qmann 7.8 MB/s 7.80 MB 82.4.221.* 2007-09-29 17:32:21 Yes qmann 12.8 MB/s 12.80 MB 82.4.221.* 2007-09-29 17:32:22 Yes qmann 8.27 MB/s 8.27 MB 82.4.221.* 2007-09-29 17:32:22 Yes qmann 2.31 MB/s 2.31 MB 82.4.221.* 2007-09-29 17:32:22 Yes qmann 2.76 MB/s 8.27 MB 82.4.221.* 2007-09-29 17:32:23 Yes qmann 4.18 MB/s 8.35 MB 82.4.221.* 2007-09-29 17:32:23 Yes qmann 1018.13 KB/s 2.98 MB 82.4.221.* 2007-09-29 17:32:24 Yes qmann 1.49 MB/s 4.46 MB 8 2.4.221.* 2007-09-29 17:32:24 Yes qmann 13 MB/s 39.01 MB 82.4.221.* 2007-09-29 17:32:24 Yes qmann 8.14 MB/s 24.43 MB 82.4.221.* 2007-09-29 17:32:24 Yes qmann 24.84 MB/s 74.51 MB 82.4.221.* 2007-09-29 17:32:24 The version of Ktorrent I'm using is 2.0.3 (using KDE 3.5.5) - anyone have any ideas how this could happen before I get banned from this tracker ? |
![]() Registered Member ![]()
|
|
![]() Registered Member ![]()
|
Looking at the number's involved and having read up on the bittorrent protocol some I'm wondering if it's possible that I had issued a stopall / startall too close together ? Could the tracker have received some start events before receiving the stop events which it should have received a few seconds previously ? i.e for the 1st one the tracker receives a stop event with a reported upload of 7.8M 1 second after it's received a start event for the same torrent on a different session ?
I was seeding 143 torrents at this particular tracker at the time if that helps. Thanks in advance, Q |
![]() Moderator ![]()
|
|
![]() Registered Member ![]()
|
|
![]() Registered Member ![]()
|
Registered users: Bing [Bot], Google [Bot]