Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#405 closed Bug (fixed)


Reported by: jah Owned by: charles
Priority: Normal Milestone: 1.00
Component: libtransmission Version: 0.90
Severity: Normal Keywords:


MAX_CONNECTED_PEERS_PER_TORRENT in peer-mgr.c does not cap peers accurately. Sometimes it works, however the behaviour is inconsistent.

eg i set it at 30, however T continues to connect to more.

Change History (4)

comment:1 Changed 15 years ago by jah

for some weird reason ~30 peers seems to be 'hardcoded' in. eg if i set it to 30, it caps peers at 30 (or within 1 or 2), however if i set it to 20, it still connects to 30 peers, but no more.

comment:2 Changed 15 years ago by charles

  • Component changed from Transmission to libtransmission
  • Version changed from 0.82+ to 0.90

comment:3 Changed 15 years ago by charles

  • Resolution set to fixed
  • Status changed from new to closed

fixed in r3769.

comment:4 Changed 15 years ago by charles

  • Milestone changed from None Set to 1.00
Note: See TracTickets for help on using tickets.