On Transmission, when Peer Limit Per Torrent is set to 100, the number of Peers Per Torrent is still limited to 60,

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Set Peer Limit Per Torrent to 100
2. Start a torrent.

What is the expected output? What do you see instead?
100 Peers should be allowed per torrent.

What version of the product are you using? On what operating system?
WLX 652 running SNAKE OS V1.3.2 (20111019) and Transmission 2.73-1 with a 2TB 
hard drive formatted as EXT3 for files and an 8GB flash drive formatted as EXT2 
for the Swapfile.

Please provide any additional information below.

Original issue reported on code.google.com by jgbrow...@gmail.com on 15 Jan 2013 at 10:31

[GoogleCodeExporter]

Sorry. This seems to have gone away. I'm not sure why this was happening. Maybe 
the server was only providing 60 peers?

Original comment by jgbrow...@gmail.com on 23 Jan 2013 at 7:48

[GoogleCodeExporter]

No idea.. maybe transmission didn't get restarted properly.

I wouldn't recommend increasing the peer number anyway. It increases 
transmissions memory usage, which can make it crash more often.

Original comment by stefansc...@googlemail.com on 24 Jan 2013 at 12:22

[GoogleCodeExporter]

It runs out of memory every 15 to 45 minutes and crashes no matter what the 
Peer Limit is set to anyway. I changed the chron on the restart to every 10 
minutes and that frees up the memory to keep it running. It's not a fix but it 
is a work around until something is fixed.

Original comment by jgbrow...@gmail.com on 25 Jan 2013 at 3:39

[GoogleCodeExporter]

It seems to work well with the restart set at 30 minutes and I have the peer 
limit set to 200. At least for one torrent at a time. It's interesting that if 
more than one torrent is added, that it crashes even if the other torrents are 
paused or queued.

Original comment by jgbrow...@gmail.com on 28 Jan 2013 at 4:56