Difference between revisions of "RTorrent"

From ArchWiki
Jump to: navigation, search
m (See also)
(Handling magnet links (opt with firefox))
(46 intermediate revisions by 23 users not shown)
Line 1: Line 1:
{{i18n|rTorrent}}
 
 
{{DISPLAYTITLE:rTorrent}}
 
{{DISPLAYTITLE:rTorrent}}
[[Category:Internet Applications (English)]]
+
[[Category:Internet Applications]]
 
+
[[es:RTorrent]]
[http://libtorrent.rakshasa.no/ rTorrent] is a quick and efficient BitTorrent client that uses the libtorrent library. It is written in C++ and uses the [[Wikipedia:ncurses|ncurses]] programming library, which means it uses a text user interface. When combined with [[GNU Screen]] and [[Secure Shell]], it becomes a convenient remote [[Wikipedia:BitTorrent (protocol)#Operation|Bitorrent client]].
+
[[ru:RTorrent]]
 +
[[zh-CN:RTorrent]]
 +
[http://libtorrent.rakshasa.no/ rTorrent] is a quick and efficient BitTorrent client that uses the libtorrent library. It is written in C++ and uses the [[Wikipedia:ncurses|ncurses]] programming library, which means it uses a text user interface. When combined with [[GNU Screen]] and [[Secure Shell]], it becomes a convenient remote [[Wikipedia:BitTorrent (protocol)#Operation|BitTorrent client]].
  
 
== Installation ==
 
== Installation ==
Install the {{Pkg|rtorrent}} package that is available in the [[community|community  repository]]:
+
[[pacman|Install]] the {{Pkg|rtorrent}} package that is available in the [[Official Repositories|official repositories]].
# pacman -S rtorrent
+
 
Alternatively, install {{AUR|rtorrent-svn}} or {{AUR|rtorrent-extended}} from the [[Arch User Repository|AUR]].
+
Alternatively, install {{AUR|rtorrent-git}} or {{AUR|rtorrent-extended}} from the [[Arch User Repository|AUR]].
  
 
== Configuration ==
 
== Configuration ==
 +
{{note|See the rTorrent wiki article on this subject for more information: [http://libtorrent.rakshasa.no/wiki/RTorrentCommonTasks Common Tasks in rTorrent for Dummies]}}
  
Before running rTorrent, download the default configuration file from the rTorrent project page and copy it to {{filename|~/.rtorrent.rc}} (see: [http://libtorrent.rakshasa.no/browser/trunk/rtorrent/doc/rtorrent.rc?format=raw Direct download]).
+
Before running rTorrent, find the example configuration file {{ic|/usr/share/doc/rtorrent/rtorrent.rc}} and copy it to {{ic|~/.rtorrent.rc}}:
 +
 
 +
$ cp /usr/share/doc/rtorrent/rtorrent.rc ~/.rtorrent.rc
 +
 
 +
=== Performance ===
 +
{{note|See the rTorrent wiki article on this subject for more information: [http://libtorrent.rakshasa.no/wiki/RTorrentPerformanceTuning Performance Tuning]}}
  
=== Peer and connection thresholds ===
 
 
The values for the following options are dependent on the system's hardware and Internet connection speed. To find the optimal values read: [http://torrentfreak.com/optimize-your-BitTorrent-download-speed Optimize Your BitTorrent Download Speed]
 
The values for the following options are dependent on the system's hardware and Internet connection speed. To find the optimal values read: [http://torrentfreak.com/optimize-your-BitTorrent-download-speed Optimize Your BitTorrent Download Speed]
 
{{bc|<nowiki>
 
{{bc|<nowiki>
Line 28: Line 34:
 
upload_rate = 28
 
upload_rate = 28
 
</nowiki>}}
 
</nowiki>}}
 +
 +
The {{ic|check_hash}} option executes a hash check when a torrent download is complete or rTorrent is started. When starting, it checks for errors in your completed files.
 +
check_hash = yes
  
 
=== Create and manage files ===
 
=== Create and manage files ===
Line 51: Line 60:
  
 
=== Additional settings ===
 
=== Additional settings ===
The {{ic|check_hash}} option executes a hash check when a torrent download is complete or rTorrent is started. When starting, it checks for errors in your completed files.
 
check_hash = yes
 
 
 
The {{ic|encryption}} option enables or disables encryption. It is very important to enable this option, not only for yourself, but also for your peers in the torrent swarm. Some users  need to obscure their bandwidth usage from their ISP. And it does not hurt to enable it even if you do not need the added security.
 
The {{ic|encryption}} option enables or disables encryption. It is very important to enable this option, not only for yourself, but also for your peers in the torrent swarm. Some users  need to obscure their bandwidth usage from their ISP. And it does not hurt to enable it even if you do not need the added security.
 
  encryption = allow_incoming,try_outgoing,enable_retry
 
  encryption = allow_incoming,try_outgoing,enable_retry
Line 65: Line 71:
 
</nowiki>}}
 
</nowiki>}}
  
{{note|More detailed configuration questions and examples are available at [http://libtorrent.rakshasa.no/wiki/RTorrentCommonTasks Common Tasks in rTorrent for Dummies].}}
+
{{note|See the rTorrent wiki article on this subject for more information: [http://libtorrent.rakshasa.no/wiki/RTorrentUsingDHT Using DHT]}}
  
 
== Key bindings ==
 
== Key bindings ==
{| class="toccolours" border="1" cellpadding="4" cellspacing="0" align="right" style="margin:5px;"
+
 
 +
rTorrent relies exclusively on keyboard shortcuts for user input. A quick reference is available in the table below. A complete guide is available on the rTorrent wiki (see:  [http://libtorrent.rakshasa.no/wiki/RTorrentUserGuide rTorrent User Guide]).
 +
 
 +
{{note|Striking {{keypress|Ctrl-q}} twice in quick succession will make rTorrent shutdown without waiting to send a stop announce to the connected trackers.}}
 +
 
 +
{| class="toccolours" border="1" cellpadding="4" cellspacing="0" style="margin:5px;"
 
|-
 
|-
 
!width="75" |Cmd
 
!width="75" |Cmd
Line 75: Line 86:
 
|Ctrl-q
 
|Ctrl-q
 
|Quit application
 
|Quit application
 +
|-
 +
|Ctrl-s
 +
|Start download. Runs hash first unless already done.
 +
|-
 +
|Ctrl-d
 +
|Stop an active download or remove a stopped download
 +
|-
 +
|Ctrl-k
 +
|Stop and close the files of an active download.
 +
|-
 +
|Ctrl-r
 +
|Initiate hash check of torrent. Without starting to download/upload.
 
|-
 
|-
 
|Left
 
|Left
Line 82: Line 105:
 
|Goes to the next screen
 
|Goes to the next screen
 
|-
 
|-
|Backspace
+
|Backspace/Return
 
|Adds the specified *.torrent
 
|Adds the specified *.torrent
 +
|-
 +
|<nowiki>a|s|d</nowiki>
 +
|<nowiki>Increase global upload throttle about 1|5|50 KB/s</nowiki>
 +
|-
 +
|<nowiki>A|S|D</nowiki>
 +
|<nowiki>Increase global download throttle about 1|5|50 KB/s</nowiki>
 +
|-
 +
|<nowiki>z|x|c</nowiki>
 +
|<nowiki>Decrease global upload throttle about 1|5|50 KB/s</nowiki>
 +
|-
 +
|<nowiki>Z|X|C</nowiki>
 +
|<nowiki>Decrease global download throttle about 1|5|50 KB/s</nowiki>
 
|}
 
|}
rTorrent relies exclusively on keyboard shortcuts for user input. A quick reference is available in the table on the right. A complete guide is available on the rTorrent wiki (see:  [http://libtorrent.rakshasa.no/wiki/RTorrentUserGuide rTorrent User Guide]).
 
 
{{note|Striking {{keypress|Ctrl-q}} twice in quick succession will make rTorrent shutdown without waiting to send a stop announce to the connected trackers.}}
 
 
 
=== Redundant mapping ===
 
=== Redundant mapping ===
 
{{Keypress|Ctrl-s}} is often used for terminal control to stop screen output while {{Keypress|Ctrl-q}} is used to start it. These mappings may interfere with rTorrent. Check to see if these terminal options are bound to a mapping:
 
{{Keypress|Ctrl-s}} is often used for terminal control to stop screen output while {{Keypress|Ctrl-q}} is used to start it. These mappings may interfere with rTorrent. Check to see if these terminal options are bound to a mapping:
Line 100: Line 131:
 
  # stty start undef
 
  # stty start undef
  
To remove these mappings automatically at startup you may add the two preceding commands to your {{filename|~/.bashrc}} file.
+
To remove these mappings automatically at startup you may add the two preceding commands to your {{ic|~/.bashrc}} file.
  
 
== Additional Tips ==
 
== Additional Tips ==
  
=== Seperate session with Screen ===
+
=== Separate session with Screen ===
 
[[GNU Screen]] is a wrapper that allows separation between the text program and the shell from which it was launched.
 
[[GNU Screen]] is a wrapper that allows separation between the text program and the shell from which it was launched.
  
Screen flow-control interferes with the {{Keypress|Ctrl-q}} mapping (see: [[#Redundant mapping|Redundant mapping]]). To disable it add the following to {{filename|~/.screenrc}}:
+
Screen flow-control interferes with the {{Keypress|Ctrl-q}} mapping (see: [[#Redundant mapping|Redundant mapping]]). To disable it add the following to {{ic|~/.screenrc}}:
 
  defflow off
 
  defflow off
  
To automatically start rTorrent within Screen, add the following to the {{filename|~/.screenrc}} configuration file:
+
An alternative is to escape the command and send it directly to rTorrent. In other words, use {{Keypress|Ctrl-a}} {{Keypress|q}} to quit rTorrent within GNU Screen.
 +
 
 +
To automatically start rTorrent within Screen, add the following to the {{ic|~/.screenrc}} configuration file:
 
  screen -t rtorrent rtorrent  
 
  screen -t rtorrent rtorrent  
  
 
==== Run as a daemon ====
 
==== Run as a daemon ====
Alternatively, Screen and rTorrent can be run together as a [[daemon]] (see also: [https://bbs.archlinux.org/viewtopic.php?id=53395 Arch Linux Forums thread], [http://forums.gentoo.org/viewtopic-t-600362-postdays-0-postorder-asc-start-0.html Gentoo Discussion Forums thread]).  
+
{{note|See the rTorrent wiki article on this subject for more information: [http://libtorrent.rakshasa.no/wiki/RTorrentCommonTasks#StartingrTorrentonSystemStartup Starting rTorrent on System Startup]}}
 +
 
 +
Alternatively, GNU Screen and rTorrent can be run together as a [[daemon]] (see also: [https://bbs.archlinux.org/viewtopic.php?id=53395 Arch Linux Forums thread], [https://forums.gentoo.org/viewtopic-t-600362-postdays-0-postorder-asc-start-0.html Gentoo Discussion Forums thread], [https://github.com/GutenYe/systemd-units/tree/master/rtorrent rtorrent-systemd]).  
  
To use this script with [[Tmux]] replace line 9 with {{ic|su rtorrent -c 'tmux -d -s rtorrent rtorrent' &> /dev/null}} (see: [https://bbs.archlinux.org/viewtopic.php?id=126718 rTorrent daemon with tmux]).
+
To use this script with [[tmux]], replace line 9 with {{ic|su - USER -c 'tmux new -s rtorrent -d rtorrent' &> /dev/null}} (see: [https://bbs.archlinux.org/viewtopic.php?id=126718 rTorrent daemon with tmux]).
  
 
With root permissions create the following file:
 
With root permissions create the following file:
  
{{hc|/etc/rc.d/rtorrent|#!/bin/bash
+
{{hc|/etc/rc.d/rtorrent|<nowiki>
 +
#!/bin/bash
  
 
. /etc/rc.conf
 
. /etc/rc.conf
Line 128: Line 164:
 
   start)
 
   start)
 
     stat_busy "Starting rtorrent"
 
     stat_busy "Starting rtorrent"
     su user -c 'screen -d -m -S rtorrent rtorrent' &> /dev/null
+
     su - USER -c 'screen -d -m -S rtorrent rtorrent' &> /dev/null
 
     if [ $? -gt 0 ]; then
 
     if [ $? -gt 0 ]; then
 
       stat_fail
 
       stat_fail
Line 155: Line 191:
 
esac
 
esac
 
exit 0
 
exit 0
}}
+
</nowiki>}}
 +
 
 +
Make sure to change USER to the username that will be running rtorrent.
  
 
Make the file executable:
 
Make the file executable:
  sudo chmod +x /etc/rc.d/rtorrent
+
  # chmod +x /etc/rc.d/rtorrent
  
Creating a {{filename|.rtorrent.rc}} file with relative paths in a user's home directory will break the rc.d script. To run multiple instances of rTorrent with relative paths under different users replace line 9 in {{filename|/etc/rc.d/rtorrent}} with the following:
+
Creating a {{ic|.rtorrent.rc}} file with relative paths in a user's home directory will break the rc.d script. To run multiple instances of rTorrent with relative paths under different users, replace line 9 in {{ic|/etc/rc.d/rtorrent}} with the following:
 
     su username -c 'cd /home/username && screen -d -m -S rtorrent rtorrent' &> /dev/null
 
     su username -c 'cd /home/username && screen -d -m -S rtorrent rtorrent' &> /dev/null
  
 
Alternatively, you can set absolute paths in the configuration file.
 
Alternatively, you can set absolute paths in the configuration file.
  
To run the daemon user multiple users create one rc.d script for each user. Then replace line 9 in {{filename|/etc/rc.d/rtorrent}} with the following:  
+
To run the daemon user multiple users create one rc.d script for each user. Then replace line 9 in {{ic|/etc/rc.d/rtorrent}} with the following:  
     su username -c 'killall -w -s 2 /usr/bin/rtorrent' &> /dev/null
+
     su - username -c 'killall -w -s 2 /usr/bin/rtorrent' &> /dev/null
  
 
To connect to the daemon process on a remote machine use [[Secure Shell|SSH]]:
 
To connect to the daemon process on a remote machine use [[Secure Shell|SSH]]:
  ssh -t rtorrent@192.168.1.10 'screen -r'
+
  $ ssh -t rtorrent@192.168.1.10 'screen -r'
 +
 
 +
Or if you used [[tmux]] instead of [[screen]]:
 +
$ ssh -t rtorrent@192.168.1.10 'tmux attach -t rtorrent'
  
 
For more information about daemon scripts see: [[Writing rc.d scripts]]
 
For more information about daemon scripts see: [[Writing rc.d scripts]]
 +
 +
This script can be found in {{aur|rtorrent-daemon}} from AUR.
  
 
Alternate scripts can be found on the [http://www.gentoo-wiki.info/Rtorrent#rtorrent Gentoo Wiki Archives], [http://codesnippets.joyent.com/posts/show/1947 Joyent CodeSnippets] and [http://www.bytetouch.com/blog/linux/how-to-rtorrent-with-screen-on-debian/ ByteTouch].
 
Alternate scripts can be found on the [http://www.gentoo-wiki.info/Rtorrent#rtorrent Gentoo Wiki Archives], [http://codesnippets.joyent.com/posts/show/1947 Joyent CodeSnippets] and [http://www.bytetouch.com/blog/linux/how-to-rtorrent-with-screen-on-debian/ ByteTouch].
 +
 +
Rtorrent service [https://wiki.archlinux.org/index.php/Systemd Systemd]
 +
 +
With root permissions create the following file:
 +
{{hc|/etc/systemd/system/rtorrent.service|<nowiki>
 +
[Unit]
 +
Description=rTorrent
 +
 +
[Service]
 +
Type=forking
 +
ExecStart=/bin/su - USER -c '/usr/bin/screen -d -m -S rtorrent /usr/bin/rtorrent'
 +
ExecStop=/usr/bin/killall -w -s 2 rtorrent
 +
 +
[Install]
 +
WantedBy=multi-user.target
 +
</nowiki>}}
 +
Add rtorrent.service:
 +
# systemctl enable rtorrent
 +
 +
Start rtorrent.service:
 +
# systemctl start rtorrent
  
 
=== Pre-allocation ===
 
=== Pre-allocation ===
Line 181: Line 245:
  
 
To make pre-allocation available, recompile libtorrent from the [[ABS]] tree with the following new switch:
 
To make pre-allocation available, recompile libtorrent from the [[ABS]] tree with the following new switch:
   ./configure --prefix=/usr --disable-debug --with-posix-fallocate
+
   $ ./configure --prefix=/usr --disable-debug --with-posix-fallocate
  
To enable it, add the following to your {{filename|~/rtorrent.rc}}:
+
To enable it, add the following to your {{ic|~/rtorrent.rc}}:
 +
{{hc|~/rtorrent.rc|<nowiki>
 
   # Preallocate files; reduces defragmentation on filesystems.
 
   # Preallocate files; reduces defragmentation on filesystems.
 
   system.file_allocate.set = yes
 
   system.file_allocate.set = yes
 +
</nowiki>}}
  
 
=== Manage completed files ===
 
=== Manage completed files ===
{{note|Currently, this part requires either the svn version of rtorrent/libtorrent or having applied the patch to 0.8.6 that adds 'equal'.}}
+
{{note|Currently, this part requires either the git version of rtorrent/libtorrent or having applied the patch to 0.8.6 that adds 'equal'.}}
  
 
{{note|If you're having trouble with this tip, it's probably easier to follow [http://libtorrent.rakshasa.no/wiki/RTorrentCommonTasks#Movecompletedtorrentstodifferentdirectorydependingonwatchdirectory this]}}
 
{{note|If you're having trouble with this tip, it's probably easier to follow [http://libtorrent.rakshasa.no/wiki/RTorrentCommonTasks#Movecompletedtorrentstodifferentdirectorydependingonwatchdirectory this]}}
  
It is possible to have rtorrent sort completed torrent data to specific folders based on which 'watch' folder you drop the *.torrent into while continuing to seed.  Many examples show how to do this with torrents downloaded by rtorrent.  The problem is when you try to drop in 100% done torrent data and then have rtorrent check the data and resume.  It will not be sorted.
+
It is possible to have rtorrent sort completed torrent data to specific folders based on which 'watch' folder you drop the *.torrent into while continuing to seed.  Many examples show how to do this with torrents downloaded by rtorrent.  The problem is when you try to drop in 100% done torrent data and then have rtorrent check the data and resume, it will not be sorted.
  
 
As a solution, use the following example in your ~/.rtorrent.rc.
 
As a solution, use the following example in your ~/.rtorrent.rc.
 
Make sure to change the paths.
 
Make sure to change the paths.
  
{{bc|
+
{{bc|1=
 
# location where new torrent data is placed, and where you should place your
 
# location where new torrent data is placed, and where you should place your
 
# 'complete' data before you place your *.torrent file into the watch folder
 
# 'complete' data before you place your *.torrent file into the watch folder
Line 233: Line 299:
 
# 2) when triggered, execute the 'movecheck1' method and check the return value.
 
# 2) when triggered, execute the 'movecheck1' method and check the return value.
 
# 3) if the 'movecheck' method returns 'true', execute the 'movedir1' method we inserted above.
 
# 3) if the 'movecheck' method returns 'true', execute the 'movedir1' method we inserted above.
# NOTE: 'branch' is an 'if' conditional statement: if(movecheck1){movedir1}
+
# NOTE-0: *Only* data that has had their hash checked manually with ^R [^R = Control r].
 +
# Or on a rtorrent restart[which initiates a hash check]. Will the data move; ~/torrents/incomplete => ~/torrents/complete for example.
 +
# NOTE-1: 'branch' is an 'if' conditional statement: if(movecheck1){movedir1}
 
system.method.set_key=event.download.hash_done,move_hashed1,"branch={$movecheck1=,movedir1=}"
 
system.method.set_key=event.download.hash_done,move_hashed1,"branch={$movecheck1=,movedir1=}"
 
}}
 
}}
Line 247: Line 315:
  
 
You can have the following in your .rtorrent.rc:
 
You can have the following in your .rtorrent.rc:
{{bc|
+
{{bc|1=
 
directory = /home/user/torrents/incomplete
 
directory = /home/user/torrents/incomplete
 
schedule = watch_directory_1,10,10,"load_start=/home/user/torrents/watch/*.torrent,d.set_custom1=/home/user/torrents/complete"
 
schedule = watch_directory_1,10,10,"load_start=/home/user/torrents/watch/*.torrent,d.set_custom1=/home/user/torrents/complete"
Line 263: Line 331:
 
Also see [http://code.google.com/p/pyroscope/ pyroscope] especially the rtcontrol examples. There is an AUR package.
 
Also see [http://code.google.com/p/pyroscope/ pyroscope] especially the rtcontrol examples. There is an AUR package.
  
==== Notificaion with Google Mail ====
+
==== Notification with Google Mail ====
  
 
Cell phone providers allow you to "email" your phone:
 
Cell phone providers allow you to "email" your phone:
<pre>
+
{{bc|<nowiki>
 
Verizon: 10digitphonenumber@vtext.com
 
Verizon: 10digitphonenumber@vtext.com
 
AT&T: 10digitphonenumber@txt.att.net
 
AT&T: 10digitphonenumber@txt.att.net
Line 289: Line 357:
 
Sasktel: 10digitphonenumber@sms.sasktel.com
 
Sasktel: 10digitphonenumber@sms.sasktel.com
 
Solo: 10digitphonenumber@txt.bell.ca
 
Solo: 10digitphonenumber@txt.bell.ca
</pre>
+
</nowiki>}}
  
*Install '''Heirloom's mailx''' program:
+
*Install Heirloom's mailx program which is provided by the {{Pkg|heirloom-mailx}} package that is found in the [[Official Repositories|official repositories]].
<pre>
+
pacman -S mailx-heirloom
+
</pre>
+
  
 
*Clear the {{ic|/etc/mail.rc}} file and enter:
 
*Clear the {{ic|/etc/mail.rc}} file and enter:
Line 300: Line 365:
 
{{Note|Older versions of Heirloom's mailx use {{ic|/etc/nail.rc}}.}}
 
{{Note|Older versions of Heirloom's mailx use {{ic|/etc/nail.rc}}.}}
  
<pre>
+
{{bc|<nowiki>
 
set sendmail="/usr/bin/mailx"
 
set sendmail="/usr/bin/mailx"
 
set smtp=smtp.gmail.com:587
 
set smtp=smtp.gmail.com:587
Line 308: Line 373:
 
set smtp-auth-user=USERNAME@gmail.com
 
set smtp-auth-user=USERNAME@gmail.com
 
set smtp-auth-password=PASSWORD
 
set smtp-auth-password=PASSWORD
</pre>
+
</nowiki>}}
  
 
Now to send the text, we must pipe a message to the mailx program.
 
Now to send the text, we must pipe a message to the mailx program.
*Make a bash script (/path/to/mail.sh):
+
*Make a Bash script:
<pre>
+
{{hc|/path/to/mail.sh|<nowiki>
 
echo "$@: Done" | mailx 5551234567@vtext.com
 
echo "$@: Done" | mailx 5551234567@vtext.com
</pre>
+
</nowiki>}}
 
Where the $@ is a variable holding all the arguments passed to our script.
 
Where the $@ is a variable holding all the arguments passed to our script.
  
*And finally, add the important ~/.rtorrent.rc line:
+
*And finally, add the important {{ic|~/.rtorrent.rc}} line:
<pre>
+
system.method.set_key = event.download.finished,notify_me,"execute=/path/to/mail.sh,$d.get_name="
system.method.set_key = event.download.finished,notify_me,"execute=/path/to/mail.sh,$d.get_name="
+
 
</pre>
+
 
Breaking it down:
 
Breaking it down:
  
Line 339: Line 403:
  
 
Then press {{keypress|9}} in your rTorrent client to see the changes in action.
 
Then press {{keypress|9}} in your rTorrent client to see the changes in action.
 +
 +
=== Manually adding trackers to torrents ===
 +
1. Select torrent to edit from rtorrent console view
 +
 +
2. Hit Ctrl-X
 +
 +
3. If you had four trackers type following lines one at a time (always press ^X first) to add four more for example:
 +
 +
d.tracker.insert="5","udp://tracker.publicbt.com:80"
 +
d.tracker.insert="6","udp://tracker.openbittorrent.com:80"
 +
d.tracker.insert="7","udp://tracker.istole.it:80"
 +
d.tracker.insert="8","udp://tracker.ccc.de:80"
  
 
== Troubleshooting ==
 
== Troubleshooting ==
Line 345: Line 421:
 
To use rTorrent with a tracker that uses HTTPS, do the following as root:
 
To use rTorrent with a tracker that uses HTTPS, do the following as root:
  
{{bc|cd /etc/ssl/certs
+
{{bc|# cd /etc/ssl/certs
wget --no-check-certificate https://www.geotrust.com/resources/root_certificates/certificates/Equifax_Secure_Global_eBusiness_CA-1.cer
+
 
mv Equifax_Secure_Global_eBusiness_CA-1.cer Equifax_Secure_Global_eBusiness_CA-1.pem
+
# wget --no-check-certificate https://www.geotrust.com/resources/root_certificates/certificates/Equifax_Secure_Global_eBusiness_CA-1.cer
c_rehash
+
 
 +
# mv Equifax_Secure_Global_eBusiness_CA-1.cer Equifax_Secure_Global_eBusiness_CA-1.pem
 +
 
 +
# c_rehash
 
}}
 
}}
  
 
And from now on run rTorrent with:
 
And from now on run rTorrent with:
  rtorrent -o http_capath=/etc/ssl/certs
+
  $ rtorrent -o http_capath=/etc/ssl/certs
  
If you use GNU Screen, update the {{filename|.screenrc}} configuration file to reflect this change:
+
If you use GNU Screen, update the {{ic|.screenrc}} configuration file to reflect this change:
  screen -t rtorrent rtorrent -o http_capath=/etc/ssl/certs
+
  $ screen -t rtorrent rtorrent -o http_capath=/etc/ssl/certs
  
 
In rTorrent 0.8.9, set {{ic|<nowiki>network.http.ssl_verify_peer.set=0</nowiki>}} to fix the problem.<sup>[https://bbs.archlinux.org/viewtopic.php?pid=981832#p981832]</sup>
 
In rTorrent 0.8.9, set {{ic|<nowiki>network.http.ssl_verify_peer.set=0</nowiki>}} to fix the problem.<sup>[https://bbs.archlinux.org/viewtopic.php?pid=981832#p981832]</sup>
Line 367: Line 446:
 
* [http://projects.cyla.homeip.net/rtwi/ rTWi] is a simple  rTorrent web interface written in PHP.
 
* [http://projects.cyla.homeip.net/rtwi/ rTWi] is a simple  rTorrent web interface written in PHP.
 
* [[Rtgui]] is a web based front end for rTorrent written in PHP and uses XML-RPC to communicate with the rTorrent client.
 
* [[Rtgui]] is a web based front end for rTorrent written in PHP and uses XML-RPC to communicate with the rTorrent client.
* [http://code.google.com/p/rutorrent/ rutorrent] and [http://forums.rutorrent.org/ Forum] - A web-based front-end with an interface very similar to uTorrent which supports many plugins and advanced features (see also: [https://bbs.archlinux.org/viewtopic.php?pid=897577#p897577 Guide for rTorrent + ruTorrent Installation]).
+
* [http://code.google.com/p/rutorrent/ rutorrent] and [http://forums.rutorrent.org/ Forum] - A web-based front-end with an interface very similar to uTorrent which supports many plugins and advanced features (see also: [[ruTorrent]] and [https://bbs.archlinux.org/viewtopic.php?pid=897577#p897577 Guide on forum]).
  
{{note|rTorrent is currently built using [http://xmlrpc-c.sourceforge.net/ XML-RPC for C/C++], which is required for some web interfaces (e.g. rutorrent).}}
+
{{note|rTorrent is currently built using [http://xmlrpc-c.sourceforge.net/ XML-RPC for C/C++], which is required for some web interfaces (e.g. ruTorrent).}}
  
 
=== XMLRPC interface ===
 
=== XMLRPC interface ===
Line 376: Line 455:
  
 
For more information see: [http://libtorrent.rakshasa.no/wiki/RTorrentXMLRPCGuide Using XMLRPC with rtorrent]
 
For more information see: [http://libtorrent.rakshasa.no/wiki/RTorrentXMLRPCGuide Using XMLRPC with rtorrent]
 +
 +
=== Handling magnet links ===
 +
If you wish to have magnet links automatically added to your watch folder, here is a script that will do the trick:
 +
 +
#!/bin/bash
 +
watch_folder=~/.rtorrent/watch
 +
cd $watch_folder 
 +
[[ "$1" =~ xt=urn:btih:([^&/]+) ]] || exit;
 +
echo "d10:magnet-uri${#1}:${1}e" > "meta-${BASH_REMATCH[1]}.torrent"
 +
 +
(adapted from http://blog.gonzih.org/blog/2012/02/17/how-to-use-magnet-links-with-rtorrent/)
 +
 +
Save it, for instance as rtorrent-magnet, give it execution permission, and place it somewhere under your $PATH. Then in Firefox:
 +
* Type about:config into the Location Bar (address bar) and press Enter.
 +
* Right-click -> New -> Boolean -> Name: network.protocol-handler.expose.magnet -> Value -> false
 +
* Next time you click a magnet link you will be asked which application to open it with. Select the script we just created and you'll be done
 +
 +
(http://kb.mozillazine.org/Register_protocol)
  
 
== See also ==
 
== See also ==
Line 381: Line 478:
 
* [[Wikipedia:Comparison of BitTorrent clients|Comparison of BitTorrent clients]] on Wikipedia
 
* [[Wikipedia:Comparison of BitTorrent clients|Comparison of BitTorrent clients]] on Wikipedia
 
* [http://community.rutorrent.org/ rTorrent Community Wiki] - A public place for information on rTorrent and any project related to rTorrent, regarding setup, configuration, operations, and development.
 
* [http://community.rutorrent.org/ rTorrent Community Wiki] - A public place for information on rTorrent and any project related to rTorrent, regarding setup, configuration, operations, and development.
* [http://code.google.com/p/pyroscope/ PyroScope] - A collection of command line tools for rTorrent. It provides commands for creating and modifying torrent files, moving data on completion without having multiple watch folders, and mass-controlling download items via rTorrent's XML-RPC interface: searching, start/stop, deleting items with or without their data, etc. It also offers a documented Python API.
+
* [http://code.google.com/p/pyroscope/ PyroScope] - A collection of command line tools for rTorrent. It provides commands for creating and modifying torrent files, moving data on completion without having multiple watch folders, and mass-controlling download items via rTorrent's XML-RPC interface: searching, start/stop, deleting items with or without their data, etc. It also offers a documented [[Python]] API.
* [http://wiki.theaveragegeek.com/howto/installing_rtorrent_and_hellanzb_on_centos5_64-bit_vps How-to Install rTorrent and Hellanzb on Centos5 64-bit VPS]
+
* [http://wiki.theaveragegeek.com/howto/installing_rtorrent_and_hellanzb_on_centos5_64-bit_vps How-to Install rTorrent and Hellanzb on CentOS 5 64-bit VPS]
 
* [http://code.google.com/p/pyroscope/wiki/DebianInstallFromSource Installation Guide for rTorrent and Pryoscope on Debian] - A collection of tools for the BitTorrent protocol and especially the rTorrent client
 
* [http://code.google.com/p/pyroscope/wiki/DebianInstallFromSource Installation Guide for rTorrent and Pryoscope on Debian] - A collection of tools for the BitTorrent protocol and especially the rTorrent client
* [http://mktorrent.sourceforge.net/ mktorrent] - A command line application used to generate torrent files, which is available as {{Pkg|mktorrent}} in the [[community repository]]
+
* [http://mktorrent.sourceforge.net/ mktorrent] - A command line application used to generate torrent files, which is available as {{Pkg|mktorrent}} in the [[Official Repositories|official repositories]].
  
  
 
'''Forum threads'''
 
'''Forum threads'''
* 2009-03-11 - Arch Linux - [https://bbs.archlinux.org/viewtopic.php?id=67304 HOWTO: rtorrent stats in conky]
+
* 2009-03-11 - Arch Linux - [https://bbs.archlinux.org/viewtopic.php?id=67304 HOWTO: rTorrent stats in Conky]
 
+
== References ==
+
* [http://jasonwryan.com/post/13494126076/rtorrent Building rtorrent on Debian Squeeze] by Jason Wryan
+

Revision as of 07:26, 5 November 2012

rTorrent is a quick and efficient BitTorrent client that uses the libtorrent library. It is written in C++ and uses the ncurses programming library, which means it uses a text user interface. When combined with GNU Screen and Secure Shell, it becomes a convenient remote BitTorrent client.

Installation

Install the rtorrent package that is available in the official repositories.

Alternatively, install rtorrent-gitAUR or rtorrent-extendedAUR from the AUR.

Configuration

Note: See the rTorrent wiki article on this subject for more information: Common Tasks in rTorrent for Dummies

Before running rTorrent, find the example configuration file /usr/share/doc/rtorrent/rtorrent.rc and copy it to ~/.rtorrent.rc:

$ cp /usr/share/doc/rtorrent/rtorrent.rc ~/.rtorrent.rc

Performance

Note: See the rTorrent wiki article on this subject for more information: Performance Tuning

The values for the following options are dependent on the system's hardware and Internet connection speed. To find the optimal values read: Optimize Your BitTorrent Download Speed

min_peers = 40
max_peers = 52

min_peers_seed = 10
max_peers_seed = 52

max_uploads = 8

download_rate = 200
upload_rate = 28

The check_hash option executes a hash check when a torrent download is complete or rTorrent is started. When starting, it checks for errors in your completed files.

check_hash = yes

Create and manage files

The directory option will determine where your torrent data will be saved. Be sure to enter the absolute path, as rTorrent may not follow relative paths:

directory = /home/[user]/torrents/

The session option allows rTorrent to save the progess of your torrents. It is recommended to create a directory called .session (e.g. $ mkdir ~/.session).

session = /home/[user]/.session/

The schedule option has rTorrent watch a particular directory for new torrent files. Saving a torrent file to this directory will automatically start the download. Remember to create the directory that will be watched (e.g. $ mkdir ~/watch). Also, be careful when using this option as rTorrent will move the torrent file to your session folder and rename it to its hash value.

schedule = watch_directory,5,5,load_start=/home/[user]/watch/*.torrent
schedule = untied_directory,5,5,stop_untied=
schedule = tied_directory,5,5,start_tied=

The following schedule option is intended to stop rTorrent from downloading data when disk space is low.

schedule = low_diskspace,5,60,close_low_diskspace=100M

Port configuration

The port_range option sets which port(s) to use for listening. It is recommended to use a port that is higher than 49152 (see: List of port numbers). Although, rTorrent allows a range of ports, a single port is recommended.

port_range = 49164-49164

Additionally, make sure port forwarding is enabled for the proper port(s) (see: Port Forward Guides).

Additional settings

The encryption option enables or disables encryption. It is very important to enable this option, not only for yourself, but also for your peers in the torrent swarm. Some users need to obscure their bandwidth usage from their ISP. And it does not hurt to enable it even if you do not need the added security.

encryption = allow_incoming,try_outgoing,enable_retry

Template:Wikipedia

This final dht option enables DHT support. DHT is common among public trackers and will allow the client to acquire more peers.

dht = auto
dht_port = 6881
peer_exchange = yes
Note: See the rTorrent wiki article on this subject for more information: Using DHT

Key bindings

rTorrent relies exclusively on keyboard shortcuts for user input. A quick reference is available in the table below. A complete guide is available on the rTorrent wiki (see: rTorrent User Guide).

Note: Striking Template:Keypress twice in quick succession will make rTorrent shutdown without waiting to send a stop announce to the connected trackers.
Cmd Action
Ctrl-q Quit application
Ctrl-s Start download. Runs hash first unless already done.
Ctrl-d Stop an active download or remove a stopped download
Ctrl-k Stop and close the files of an active download.
Ctrl-r Initiate hash check of torrent. Without starting to download/upload.
Left Returns to the previous screen
Right Goes to the next screen
Backspace/Return Adds the specified *.torrent
a|s|d Increase global upload throttle about 1|5|50 KB/s
A|S|D Increase global download throttle about 1|5|50 KB/s
z|x|c Decrease global upload throttle about 1|5|50 KB/s
Z|X|C Decrease global download throttle about 1|5|50 KB/s

Redundant mapping

Template:Keypress is often used for terminal control to stop screen output while Template:Keypress is used to start it. These mappings may interfere with rTorrent. Check to see if these terminal options are bound to a mapping:

$ stty -a
...
swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V;
...

To remove the mappings, change the terminal characteristics to undefine the aforementioned special characters (i.e. stop and start):

# stty stop undef
# stty start undef

To remove these mappings automatically at startup you may add the two preceding commands to your ~/.bashrc file.

Additional Tips

Separate session with Screen

GNU Screen is a wrapper that allows separation between the text program and the shell from which it was launched.

Screen flow-control interferes with the Template:Keypress mapping (see: Redundant mapping). To disable it add the following to ~/.screenrc:

defflow off

An alternative is to escape the command and send it directly to rTorrent. In other words, use Template:Keypress Template:Keypress to quit rTorrent within GNU Screen.

To automatically start rTorrent within Screen, add the following to the ~/.screenrc configuration file:

screen -t rtorrent rtorrent 

Run as a daemon

Note: See the rTorrent wiki article on this subject for more information: Starting rTorrent on System Startup

Alternatively, GNU Screen and rTorrent can be run together as a daemon (see also: Arch Linux Forums thread, Gentoo Discussion Forums thread, rtorrent-systemd).

To use this script with tmux, replace line 9 with su - USER -c 'tmux new -s rtorrent -d rtorrent' &> /dev/null (see: rTorrent daemon with tmux).

With root permissions create the following file:

/etc/rc.d/rtorrent
#!/bin/bash

. /etc/rc.conf
. /etc/rc.d/functions

case "$1" in
  start)
    stat_busy "Starting rtorrent"
    su - USER -c 'screen -d -m -S rtorrent rtorrent' &> /dev/null
    if [ $? -gt 0 ]; then
      stat_fail
    else
      add_daemon rtorrent
      stat_done
    fi
    ;;
  stop)
    stat_busy "Stopping rtorrent"
    killall -w -s 2 /usr/bin/rtorrent &> /dev/null
    if [ $? -gt 0 ]; then
      stat_fail
    else
      rm_daemon rtorrent
      stat_done
    fi
    ;;
  restart)
    $0 stop
    sleep 1
    $0 start
    ;;
  *)
    echo "usage: $0 {start|stop|restart}"
esac
exit 0

Make sure to change USER to the username that will be running rtorrent.

Make the file executable:

# chmod +x /etc/rc.d/rtorrent

Creating a .rtorrent.rc file with relative paths in a user's home directory will break the rc.d script. To run multiple instances of rTorrent with relative paths under different users, replace line 9 in /etc/rc.d/rtorrent with the following:

   su username -c 'cd /home/username && screen -d -m -S rtorrent rtorrent' &> /dev/null

Alternatively, you can set absolute paths in the configuration file.

To run the daemon user multiple users create one rc.d script for each user. Then replace line 9 in /etc/rc.d/rtorrent with the following:

   su - username -c 'killall -w -s 2 /usr/bin/rtorrent' &> /dev/null

To connect to the daemon process on a remote machine use SSH:

$ ssh -t rtorrent@192.168.1.10 'screen -r'

Or if you used tmux instead of screen:

$ ssh -t rtorrent@192.168.1.10 'tmux attach -t rtorrent'

For more information about daemon scripts see: Writing rc.d scripts

This script can be found in rtorrent-daemonAUR from AUR.

Alternate scripts can be found on the Gentoo Wiki Archives, Joyent CodeSnippets and ByteTouch.

Rtorrent service Systemd

With root permissions create the following file:

/etc/systemd/system/rtorrent.service
[Unit]
Description=rTorrent

[Service]
Type=forking
ExecStart=/bin/su - USER -c '/usr/bin/screen -d -m -S rtorrent /usr/bin/rtorrent'
ExecStop=/usr/bin/killall -w -s 2 rtorrent

[Install]
WantedBy=multi-user.target

Add rtorrent.service:

# systemctl enable rtorrent

Start rtorrent.service:

# systemctl start rtorrent

Pre-allocation

The rTorrent package in the community repository lacks pre-allocation. Compiling rTorrent with pre-allocation allows files to be allocated before downloading the torrent. The major benefit is that it limits and avoids fragmentation of the filesystem. However, this introduces a delay during the pre-allocation if the filesystem does not support the fallocate syscall natively.

Therefore this switch is recommended for xfs, ext4 and btrfs filesystems, which have native fallocate syscall support. They will see no delay during preallocation and no fragmented filesystem. Pre-allocation on others filesystems will cause a delay but will not fragment the files.

To make pre-allocation available, recompile libtorrent from the ABS tree with the following new switch:

 $ ./configure --prefix=/usr --disable-debug --with-posix-fallocate

To enable it, add the following to your ~/rtorrent.rc:

~/rtorrent.rc
  # Preallocate files; reduces defragmentation on filesystems.
  system.file_allocate.set = yes

Manage completed files

Note: Currently, this part requires either the git version of rtorrent/libtorrent or having applied the patch to 0.8.6 that adds 'equal'.
Note: If you're having trouble with this tip, it's probably easier to follow this

It is possible to have rtorrent sort completed torrent data to specific folders based on which 'watch' folder you drop the *.torrent into while continuing to seed. Many examples show how to do this with torrents downloaded by rtorrent. The problem is when you try to drop in 100% done torrent data and then have rtorrent check the data and resume, it will not be sorted.

As a solution, use the following example in your ~/.rtorrent.rc. Make sure to change the paths.

# location where new torrent data is placed, and where you should place your
# 'complete' data before you place your *.torrent file into the watch folder
directory = /home/user/torrents/incomplete

# schedule a timer event named 'watch_directory_1':
# 1) triggers 10 seconds after rtorrent starts
# 2) triggers at 10 second intervals thereafter
# 3) Upon trigger, attempt to load (and start) new *.torrent files found in /home/user/torrents/watch/
# 4) set a variable named 'custom1' with the value "/home/user/torrents/complete"
# NOTE: if you do not want it to automatically start the torrent, change 'load_start' to 'load'
schedule = watch_directory_1,10,10,"load_start=/home/user/torrents/watch/*.torrent,d.set_custom1=/home/user/torrents/complete"

# insert a method with the alias 'checkdirs1'
# 1) returns true if the current path of the torrent data is not equal to the value of custom1
# 2) otherwise, returns false
system.method.insert=checkdirs1,simple,"not=\"$equal={d.get_custom1=,d.get_base_path=}\""

# insert a method with the alias 'movecheck1'
# 1) returns true if all 3 commands return true ('result of checkdirs1' && 'torrent is 100% done', 'custom1 variable is set')
# 2) otherwise, returns false
system.method.insert=movecheck1,simple,"and={checkdirs1=,d.get_complete=,d.get_custom1=}"

# insert a method with the alias 'movedir1'
# (a series of commands, separated by ';') 
# 1) "set path of torrent to equal the value of custom1";
# 2) "mv -u <current data path> <custom1 path>";
# 3) "clear custom1", "stop the torrent","resume the torrent"
# 4) stop the torrent
# 5) start the torrent (to get the torrent to update the 'base path')
system.method.insert=movedir1,simple,"d.set_directory=$d.get_custom1=;execute=mv,-u,$d.get_base_path=,$d.get_custom1=;d.set_custom1=;d.stop=;d.start="

# set a key with the name 'move_hashed1' that is triggered by the hash_done event.
# 1) When hashing of a torrent completes, this custom key will be triggered.
# 2) when triggered, execute the 'movecheck1' method and check the return value.
# 3) if the 'movecheck' method returns 'true', execute the 'movedir1' method we inserted above.
# NOTE-0: *Only* data that has had their hash checked manually with ^R [^R = Control r].
# Or on a rtorrent restart[which initiates a hash check]. Will the data move; ~/torrents/incomplete => ~/torrents/complete for example.
# NOTE-1: 'branch' is an 'if' conditional statement: if(movecheck1){movedir1}
system.method.set_key=event.download.hash_done,move_hashed1,"branch={$movecheck1=,movedir1=}"

You can add additional watch folders and rules should you like to sort your torrents into special folders.

For example, if you would like the torrents to download in:

/home/user/torrents/incomplete

and then sort the torrent data based on which folder you dropped the *.torrent into:

/home/user/torrents/watch => /home/user/torrents/complete
/home/user/torrents/watch/iso => /home/user/torrents/complete/iso
/home/user/torrents/watch/music => /home/user/torrents/complete/music

You can have the following in your .rtorrent.rc:

directory = /home/user/torrents/incomplete
schedule = watch_directory_1,10,10,"load_start=/home/user/torrents/watch/*.torrent,d.set_custom1=/home/user/torrents/complete"

schedule = watch_directory_2,10,10,"load_start=/home/user/torrents/watch/iso/*.torrent,d.set_custom1=/home/user/torrents/complete/iso"

schedule = watch_directory_3,10,10,"load_start=/home/user/torrents/watch/music/*.torrent,d.set_custom1=/home/user/torrents/complete/music"

system.method.insert=checkdirs1,simple,"not=\"$equal={d.get_custom1=,d.get_base_path=}\""
system.method.insert=movecheck1,simple,"and={checkdirs1=,d.get_complete=,d.get_custom1=}"
system.method.insert=movedir1,simple,"d.set_directory=$d.get_custom1=;execute=mv,-u,$d.get_base_path=,$d.get_custom1=;d.set_custom1=;d.stop=;d.start="
system.method.set_key=event.download.hash_done,move_hashed1,"branch={$movecheck1=,movedir1=}"

Also see pyroscope especially the rtcontrol examples. There is an AUR package.

Notification with Google Mail

Cell phone providers allow you to "email" your phone:

Verizon: 10digitphonenumber@vtext.com
AT&T: 10digitphonenumber@txt.att.net
Former AT&T customers: 10digitphonenumber@mmode.com
Sprint: 10digitphonenumber@messaging.sprintpcs.com
T-Mobile: 10digitphonenumber@tmomail.net
Nextel: 10digitphonenumber@messaging.nextel.com
Cingular: 10digitphonenumber@cingularme.com
Virgin Mobile: 10digitphonenumber@vmobl.com
Alltel: 10digitphonenumber@alltelmessage.com OR
10digitphonenumber@message.alltel.com
CellularOne: 10digitphonenumber@mobile.celloneusa.com
Omnipoint: 10digitphonenumber@omnipointpcs.com
Qwest: 10digitphonenumber@qwestmp.com
Telus: 10digitphonenumber@msg.telus.com
Rogers Wireless: 10digitphonenumber@pcs.rogers.com
Fido: 10digitphonenumber@fido.ca
Bell Mobility: 10digitphonenumber@txt.bell.ca
Koodo Mobile: 10digitphonenumber@msg.koodomobile.com
MTS: 10digitphonenumber@text.mtsmobility.com
President's Choice: 10digitphonenumber@txt.bell.ca
Sasktel: 10digitphonenumber@sms.sasktel.com
Solo: 10digitphonenumber@txt.bell.ca
  • Clear the /etc/mail.rc file and enter:
Note: Older versions of Heirloom's mailx use /etc/nail.rc.
set sendmail="/usr/bin/mailx"
set smtp=smtp.gmail.com:587
set smtp-use-starttls
set ssl-verify=ignore
set ssl-auth=login
set smtp-auth-user=USERNAME@gmail.com
set smtp-auth-password=PASSWORD

Now to send the text, we must pipe a message to the mailx program.

  • Make a Bash script:
/path/to/mail.sh
echo "$@: Done" | mailx 5551234567@vtext.com

Where the $@ is a variable holding all the arguments passed to our script.

  • And finally, add the important ~/.rtorrent.rc line:
system.method.set_key = event.download.finished,notify_me,"execute=/path/to/mail.sh,$d.get_name="

Breaking it down:

notify_me is the command id, which may be used by other commands, it can be just about anything you like, so long as it is unique.

execute= is the rtorrent command, in this case to execute a shell command.

/path/to/mail.sh is the name of our script (or whatever command you want to execute) followed by a comma separated list of all the switches/arguments to be passed.

$d.get_name= 'd' is an alias to whatever download triggered the command, get_name is a function which returns the name of our download, and the '$' tells rTorrent to replace the command with its output before it calls execute.

The end result? When that torrent, 'All Live Nudibranches', that we started before leaving for work finishes, we will be texted:

All Live Nudibranches: Done

Displaying active torrents

The rtorrent doesn't list the active tab properly by default, add this line to your .rtorrent.rc to show only active torrents

schedule = filter_active,30,30,"view_filter = active,\"or={d.get_up_rate=,d.get_down_rate=}\""

Then press Template:Keypress in your rTorrent client to see the changes in action.

Manually adding trackers to torrents

1. Select torrent to edit from rtorrent console view

2. Hit Ctrl-X

3. If you had four trackers type following lines one at a time (always press ^X first) to add four more for example:

d.tracker.insert="5","udp://tracker.publicbt.com:80"
d.tracker.insert="6","udp://tracker.openbittorrent.com:80"
d.tracker.insert="7","udp://tracker.istole.it:80"
d.tracker.insert="8","udp://tracker.ccc.de:80"

Troubleshooting

CA certificates

To use rTorrent with a tracker that uses HTTPS, do the following as root:

# cd /etc/ssl/certs

# wget --no-check-certificate https://www.geotrust.com/resources/root_certificates/certificates/Equifax_Secure_Global_eBusiness_CA-1.cer

# mv Equifax_Secure_Global_eBusiness_CA-1.cer Equifax_Secure_Global_eBusiness_CA-1.pem

# c_rehash

And from now on run rTorrent with:

$ rtorrent -o http_capath=/etc/ssl/certs

If you use GNU Screen, update the .screenrc configuration file to reflect this change:

$ screen -t rtorrent rtorrent -o http_capath=/etc/ssl/certs

In rTorrent 0.8.9, set network.http.ssl_verify_peer.set=0 to fix the problem.[1]

For more information see: rTorrent Error & CA Certificate and rTorrent Certificates Problem

Web interface

There are numerous web interfaces and front ends for rTorrent including:

  • WTorrent is a web interface to rtorrent programmed in php using Smarty templates and XMLRPC for PHP library.
  • nTorrent is a graphical user interface client to rtorrent (a cli torrent client) written in Java.
  • rTWi is a simple rTorrent web interface written in PHP.
  • Rtgui is a web based front end for rTorrent written in PHP and uses XML-RPC to communicate with the rTorrent client.
  • rutorrent and Forum - A web-based front-end with an interface very similar to uTorrent which supports many plugins and advanced features (see also: ruTorrent and Guide on forum).
Note: rTorrent is currently built using XML-RPC for C/C++, which is required for some web interfaces (e.g. ruTorrent).

XMLRPC interface

If you want to use rtorrent with some web interfaces (e.g. rutorrent) you need to add the following line to the configuration file:

scgi_port = localhost:5000

For more information see: Using XMLRPC with rtorrent

Handling magnet links

If you wish to have magnet links automatically added to your watch folder, here is a script that will do the trick:

#!/bin/bash
watch_folder=~/.rtorrent/watch
cd $watch_folder  
[[ "$1" =~ xt=urn:btih:([^&/]+) ]] || exit;
echo "d10:magnet-uri${#1}:${1}e" > "meta-${BASH_REMATCH[1]}.torrent"

(adapted from http://blog.gonzih.org/blog/2012/02/17/how-to-use-magnet-links-with-rtorrent/)

Save it, for instance as rtorrent-magnet, give it execution permission, and place it somewhere under your $PATH. Then in Firefox:

  • Type about:config into the Location Bar (address bar) and press Enter.
  • Right-click -> New -> Boolean -> Name: network.protocol-handler.expose.magnet -> Value -> false
  • Next time you click a magnet link you will be asked which application to open it with. Select the script we just created and you'll be done

(http://kb.mozillazine.org/Register_protocol)

See also


Forum threads