rTorrent is a highly configurable torrent client based on libtorrent and ncurses.
|color||No||Add custom color support for torrent list|
|daemon||No||Uses app-misc/screen to daemonize this application|
|debug||No||No||Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see http://www.gentoo.org/proj/en/qa/backtraces.xml|
|ipv6||No||Adds support for IP version 6|
|test||No||No||Workaround to pull in packages needed to run with FEATURES=test. Portage-2.1.2 handles this internally, so don't set it in make.conf/package.use anymore|
|xmlrpc||No||Support for xml-rpc library|
The RTorrent configuration is stored in the user's ~/.rtorrent.rc. A lot can be configured, for this reason, the configuration is divided in sections.
These options are pretty straightforward:
Watching a Directory
You can configure rTorrent to watch one or more directories for new torrent files and queue them automatically. You can also set a download directory for each watch directory (rather than downloading to the default download directory).
You can control seed time by making it dependent on each torrent's ratio. Each torrent is seeded for a minimum of min.set percent. if a total of upload.set has been uploaded. If upload.set is not reached, it will seed a maximum of max.set percent. Read the wiki on the libtorrent site for different ratio groups.
Adding a self-signed certificate
Some trackers use SSL certificates, however most are not signed for various reasons. rTorrent uses the database located in /etc/ssl/certs/ca-certificates.crt. You also may want to use HTTPS because some ISPs (like Comcast) perform bandwidth shaping, effectively slowing down BitTorrent (regardless of whether your use is legitimate).
Add a certificate (if the domain was mytracker.net and the port was 443):
You need to re-hash after adding a certificate:
Try with curl:
You should not get a warning regarding the self-signed certificate.
Restart rTorrent. If using the daemon: