What steps will reproduce the problem?
1. Set peer-limit-per-torrent in transmission config (eg. 50)
2. Add the server to transmission-remote-gui via Torrent > Connect to
Tranmission > New Connection...
3. Add torrent in transmission-remote-gui. 'Max Peers' under general tab of
this torrent will reflect the number (seems to also be the actual max peers
that will connect, too)
4. Stop transmission, change peer-limit-per-torrent in transmission config to a
new value (100, for example), and restart transmission
5. Any new torrents added by transmission-remote-gui will be added with max
peers of 50 (instead of the correct 100) until the connection is deleted from
transmission-remote-gui and readded. Adding torrents with the web UI reflects
the current peer-limit-per-torrent (correct behaviour).
What is the expected output? What do you see instead?
Any added torrent is added with the per torrent peer limit setting from when
the connection was added to remote-gui rather than the current (or at least
when the current connection was established)
What version of the product are you using? On what operating system?
Remote GUI 5.0.1 on win7 home premium x64, Transmission 2.82 drobo build from
drobo dashboard
Please provide any additional information below.
I also noticed that upon restart all RUNNING torrents had their max peers
updated to peer-limit-per-torrent value but not stopped ones. I assume this is
transmission behaviour and not remote-gui's but I figured I'd mention it anyway.
Original issue reported on code.google.com by nova2...@gmail.com on 11 Mar 2014 at 5:50
Original issue reported on code.google.com by
nova2...@gmail.comon 11 Mar 2014 at 5:50