Package: transmission Version: 2.52-1 Severity: minor Hi,
The setting for 'maximum peers per torrent' seems as if it should affect all torrents currently in Transmission's queue. However, in fact this seems to only affect torrents that are added *after* this value has been set. So if I add a torrent with the limit at the default, and then I later want to lower this value to free up some bandwidth, this won't apply to the existing torrent, unless I remove the torrent and re-add it. To reproduce: find a very popular torrent with more than 20 seeders. Set 'maximum peers per torrent' to 10, add the torrent. Transmission's status will say "Downloading from <x> of 10 connected peers". Now go to Edit > Preferences > Network and set "Maximum peers per torrent" to 20. I would expect the existing torrent to adjust to the new global limit and connect to more seeders -- this is what happens with the "Maximum peers overall" value, actually. But instead, the torrent will stay connected to only 10 seeders. If you remove and add the torrent again after setting the value, it will correctly connect to 20 seeders. Cheers, David -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages transmission depends on: ii transmission-cli 2.52-1 ii transmission-common 2.52-1 ii transmission-gtk 2.52-1 transmission recommends no packages. transmission suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
