-
-
Notifications
You must be signed in to change notification settings - Fork 408
Config Guide
Contents
See rTorrent Configuration Template for a modern rTorrent configuration that provides a good starting point. The following sub-sections describe some of the essential settings you must have in a common configuration like that, plus some advanced settings you can add, depending on what your needs are.
Additionally, the Common Tasks in rTorrent page lists many useful things to have in a configuration, and also some tips regarding maintenance tasks.
Adding the session.path.set command will enable session management, which means the torrent files and status information for all open downloads will be stored in this directory. When restarting rTorrent all torrents previously loaded will be restored. Only one instance of rTorrent should be used with each session directory, though at the moment no locking is done. An empty string will disable the session handling.
✅ This is already contained in CONFIG-Template.
The client may be configured to check a directory for new torrents and load them. Torrents loaded in this manner will be tied to the file's path. This means when the torrent file is deleted the torrent may be stopped (requires additional configuration), and when the item is removed the torrent file is, too. Note that you can untie an item by using the U key (which will delete the tied file), and using ^K also implictly unties an item.
See also the Watch Directories page.
✅ This is already contained in CONFIG-Template.
These pages and the following sections cover information that you don't need when you start out (i.e. read at your leisure), or only apply to a small number of users.