I've been running torrentflux-b4rt for a long time now on my server. (http://tf-b4rt.berlios.de/) For many years, I was using "bittornado" by default, without really caring. Recently however, bitornado appears to fail at downloading at decent speeds. This setup was running on Ubuntu server LTS 8.04.
On my desktop, Ubuntu 10.04, I tried out the latest transmission GUI (2.05) to test if it was my ISP limiting me, or the bittornado client on the server. As it turns out, the latest Transmission rocks! Got nearly max download throughput from a torrent file. Impressive.
Now, I have been hacking around for a few hours now getting transmission to work with torrentflux-b4rt. TF-b4rt /does/ship with some transmission clients, but apparently it has to patch it some way (http://wiki.amahi.org/index.php/TorrentFlux-b4rt). I followed those instructions to get transmission 1.50 CLI patched, and I'm running transmission 1.93 on the server now. (again, to clarify, I'm running the ubuntu supplied version of transmission on the server, with a self-compiled transmissioncli @ version 1.50 ... because that is the latest version that a patch exists for getting transmissionCLI to work with b4rt...)
Unfortunately, with the older version of the CLI, I don't see any way to control the max peer connections.
Code: Select all
fermulator@fermmy-server:~$ transmissioncli -v Transmission 1.50 (7887) - http://www.transmissionbt.com/ - modified for Torrentflux-b4rt No torrent specified! fermulator@fermmy-server:~$ transmissioncli -h Transmission 1.50 (7887) - http://www.transmissionbt.com/ - modified for Torrentflux-b4rt A fast and easy BitTorrent client Usage: transmission [options] <torrent-filename> Options: -h --help Display this help page and exit -a --announce <url> Set the new torrent's announce URL -b --blocklist Enable peer blocklists -B --no-blocklist Disable peer blocklists -c --comment <comment> Set the new torrent's comment -d --downlimit <speed> Set max download speed in KB/s -D --no-downlimit Don't limit the download speed -er --encryption-required Encrypt all peer connections -ep --encryption-preferred Prefer encrypted peer connections -et --encryption-tolerated Prefer unencrypted peer connections -f --finish <script> Run a script when the torrent finishes -g --config-dir <path> Where to find configuration files -i --info Show torrent details and exit -m --portmap Enable portmapping via NAT-PMP or UPnP -M --no-portmap Disable portmapping -n --new <source> Create a new torrent -p --port <port> Port for incoming peers (Default: 51413) -r --private Set the new torrent's 'private' flag -s --scrape Scrape the torrent and exit -t --tos <tos> Peer socket TOS (0 to 255, default=8) -u --uplimit <speed> Set max upload speed in KB/s -U --no-uplimit Don't limit the upload speed -v --verify Verify the specified torrent -w --download-dir <path> Where to save downloaded data -E --display-interval <int> Time between updates of stat-file (default = 5) -L --seedlimit <int> Seed-Limit (Percent) to reach before shutdown -O --owner <string> Name of the owner (default = 'n/a') -W --die-when-done <args> Auto-Shutdown when done (0 = Off, 1 = On, default = 0)
Code: Select all
"max-peers-global": 200 "peer-limit-global": 200 "peer-limit-per-torrent": 30
Can anyone suggest/comment if the transmission CLI 1.50 has the capability to control the global peer limit? (I had to compile it, so if it's a hard coded value in this version, maybe I can edit that value pre-compile? that would be sufficient...)