I am trying to get rtorrent to run as a systemd service, but the service wouldn't start. Here's the config file and any log I can get. Ask for more info if you need to. I am running:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.2 LTS
Release:        20.04
Codename:       focal

$ systemctl status rtorrent
● rtorrent.service - rTorrent
     Loaded: loaded (/etc/systemd/system/rtorrent.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Thu 2021-05-27 08:52:43 EEST; 5min ago
    Process: 20199 ExecStart=/usr/bin/tmux new-session -d -P -s rt -n rtorrent /usr/bin/rtorrent (code=exited, status=0/SUCCESS)
    Process: 20205 ExecStop=/usr/bin/tmux send-keys -t rt:rtorrent C-q (code=exited, status=1/FAILURE)
   Main PID: 20201 (code=exited, status=0/SUCCESS)

May 27 08:52:43 $MACHINE systemd[1] : Starting rTorrent...
May 27 08:52:43 $MACHINE tmux: rt:
May 27 08:52:43 $MACHINE systemd[1] : Started rTorrent.
May 27 08:52:43 $MACHINE tmux: no server running on /tmp/tmux-110/default
May 27 08:52:43 $MACHINE systemd[1] : rtorrent.service: Control process exited, code=exited, status=1/FAILURE
May 27 08:52:43 $MACHINE systemd[1] : rtorrent.service: Failed with result 'exit-code'.

The config file..

/etc/systemd/system/rtorrent.service 
[Unit]
Description=rTorrent
Requires=network.target local-fs.target

[Service]
Type=forking
KillMode=none
User=rt
Group=adm
ExecStart=/usr/bin/tmux new-session -d -P -s rt -n rtorrent /usr/bin/rtorrent
ExecStop=/usr/bin/tmux send-keys -t rt:rtorrent C-q
WorkingDirectory=/tmp/tmux-110/

[Install]
WantedBy=multi-user.target

Some more logs:

$ journalctl -u rtorrent
May 27 08:52:43 $MACHINE systemd[1] : Starting rTorrent...
May 27 08:52:43 $MACHINE tmux: rt:
May 27 08:52:43 $MACHINE systemd[1] : Started rTorrent.
May 27 08:52:43 $MACHINE tmux: no server running on /tmp/tmux-110/default
May 27 08:52:43 $MACHINE systemd[1] : rtorrent.service: Control process exited, code=exited, status=1/FAILURE
May 27 08:52:43 $MACHINE systemd[1] : rtorrent.service: Failed with result 'exit-code'.

So far I have added the user rt to the adm group, but I can't figure it out why tmux can't be started as rt. I also authorized rt user to launch services thanks to the enable-linger option: loginctl enable-linger rt I first added the rt user with:sudo adduser --system --gecos "rTorrent Client" --disabled-password --group --home /home/rt rt. How to make rtorrent run as systemd service with tmuxas a dedicated user? Or is there any other way to run it as service with systemd? Any help is really appreciated. **UPDATE:** So, just to get a fresh start, I have created a new user named rtorrent with: sudo adduser --system --gecos "rTorrent System Client" --disabled-password --group --home /home/rtorrent rtorrent and changed the /etc/systemd/system/rtorrent.service file to this (also adding system.daemon = true in /home/rtorrent/.rtorrent.rc, because of this post ):

[Unit]
Description=rTorrent System Daemon
After=network.target

[Service]
Type=simple
User=rtorrent
Group=rtorrent

ExecStartPre=-/bin/rm -f /home/rtorrent/.session/rtorrent.lock
ExecStart=/usr/bin/rtorrent -o import=/home/rtorrent/.rtorrent.rc
Restart=on-failure
RestartSec=3

[Install]
WantedBy=multi-user.target

But after all I get this error:

$ systemctl status rtorrent
● rtorrent.service - rTorrent System Daemon
     Loaded: loaded (/etc/systemd/system/rtorrent.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Thu 2021-05-27 10:12:26 EEST; 2s ago
    Process: 22855 ExecStartPre=/bin/rm -f /home/rtorrent/.session/rtorrent.lock (code=exited, status=0/SUCCESS)
    Process: 22856 ExecStart=/usr/bin/rtorrent -o import=/home/rtorrent/.rtorrent.rc (code=exited, status=255/EXCEPTION)
   Main PID: 22856 (code=exited, status=255/EXCEPTION)

Why is this happening? What I am doing wrong? **UPDATE 2:** One more thing, This post suggest not dropping any files in the /etc/systemd/system/, but instead, to drop them in /usr/local/lib/systemd/system which in Debian based systems is in /lib/systemd/system. Therefore, I moved the unit-file there and when enabling it, it automatically created a symlink to /etc/systemd/system/. But still,, I get this error:

$ sudo systemctl status rtorrent
● rtorrent.service - rTorrent System Daemon
     Loaded: loaded (/lib/systemd/system/rtorrent.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Thu 2021-05-27 10:39:14 EEST; 924ms ago
    Process: 24530 ExecStartPre=/bin/rm -f /home/rtorrent/.session/rtorrent.lock (code=exited, status=0/SUCCESS)
    Process: 24531 ExecStart=/usr/bin/rtorrent -o import=/home/rtorrent/.rtorrent.rc (code=exited, status=255/EXCEPTION)
   Main PID: 24531 (code=exited, status=255/EXCEPTION)

I would like to create a XMLRPC command and add to rtorrent.rc to schedule pausing and resuming all torrents. Reading the docs I figured out the following but something is missing and the command doesn't work. Command to pause all torrents at a given time every 24 hours:

= pause_torrents, 01:10:00, 24:00:00, ((d.multicall2=,d.pause=))

For resuming would just use d.resume command. For stopping or starting would use d.stop or d.start respectively. Can you provide the solution?

Let's say I'm using rTorrent and I accidentally delete the underlying file. But the torrent still shows in the rTorrent download list, is there a method to re-download the same thing? Or.. better, since rTorrent still has an open file handle to move it back to the location?

rtorrent provides a nice script for moving downloads to a directory based on label or name
i'm trying to configure the script using my local folder ~/files
It tries to use a "work" directory

# Determine target path (adapt this to your needs)
set_target_path() {
    local month=$(date +'%Y-%m')

    # Only move data downloaded into a "work" directory
    if egrep >/dev/null "/work/" /dev/null "~/files/" <<<"${base_path}/"; then
        # Make sure the target directory is on the same drive as "work", else leave it alone
        work_dir=$(sed -re 's~(^.+~/files/).*~\1~' <<<"${base_path}/")
        test $(fs4path "$work_dir") == $(fs4path "$(dirname ${base_path})") || return
    else
        return  # no "work" component in data path (pre-determined path)
    fi

restarted rtorrent and nothing yet

I've got a seedbox with rTorrent (and ruTorrent) installed, and I'm trying to automate as much as possible... Currently, I've got this in my rtorrent.rc to move completed files to ~/Download: system.method.set_key = event.download.finished,move_complete,"execute=mv,-u,$d.get_base_path=,~/Download/;d.set_directory=~/Download/" And then I've got a script that rsyncs those completed files back to my home computer... I've got ruTorrent set to apply labels to torrents, and I'd like to move files according to the labels instead of moving them all to the same folder. I can't find any documentation at all, though. There are lots of examples of configuring rTorrent for 'common tasks', but nothing that I've been able to use to infer how to even check labels, never mind move completed torrents according to the labels...

How do I get rtorrent to use a socks5 proxy? I've tried to get socks5 to work with rtorrent, but it doesn't seem to have any impact. Setup the socks5 proxy on port 9800: ssh -ND 9800 user@otherhost in .rtorrent.rc http_proxy=127.0.0.7:9800 proxy_address=127.0.0.7:9800 It cannot download any data from tracker. Tracker: [Server returned nothing (no headers, no data)] And my ip does not appear to use the IP from "otherhost" when I check with http://www.checkmytorrentip.com/ I also tried using tsocks rtorrent server = 127.0.0.1 eserver_type = 5 server_port = 9800 This shows my IP as coming from 'otherhost', but after a few seconds rtorrent freezes up. I am using rTorrent 0.9.2/0.13.2

I'm trying to start a docker image on my machine (fresh fedora 37 server (with kernel and arch: 6.0.8-300.fc37.x86_64 also tried on aarch64 - same problem) install, with docker (20.10.21) and for some reason it uses all the resources (cpu, ram) like it was a fork bomb (except it using all ram too). The image what I try to run is docker run -it --rm jesec/rtorrent I am interested why this is happening in general, my intention is not to run this specific image. Also it is not behaving the same way on different machines (the OS is identical), on some machines I get: > rtorrent: std::bad_alloc

I run rtorrent remotely on a seedbox. When I log in with a web interface I'm able to start torrents, and when torrent files get dropped into my watched folder that works too. However, when I try to start them by SSHing in to my seedbox and -r resuming the screen session that contains my instance of rtorrent, I can't seem to use the Ctrl+S keyboard shortcut to start torrents. I can stop and delete them with the Ctrl+D shortcut, and as far as I can tell all the other keyboard shortcuts work. I've tried this from the Terminal app in OSX and from Cygwin on Windows. Thanks for your insight!

I've used rtorrent on some magnetic-links and it created some "meta"-files, which seemed to be named by the hash... Is there a way to somehow use these meta-files to start rtorrent to download the torrents, rather than having to locate the actual magnet? E.g. rtorrent 637778299.meta or somethin?

I have box with internet connection and limited space. I have also much more space offline. I download fime files with **rTorrent**, share them for some time, then move them to offline space to be able download more files. **Sometimes later somebody asks me to share those files again, so I would like to put them back to sharing, but I do not know how.** --- Details 1. **I download magnet URL** ( magnet:?xt=urn:btih:12345.... ) 2. cd ~/torrents 3. echo "d10:magnet-uri${#1}:${1}e" > "meta-${BASH_REMATCH}.torrent" # create meta-12345...torrent 4. rtorrent downloads 12345...meta to ~/torrents/Downloads 5. rtorrent downloads and share ~/torrents/Downloads/some_dir/some_files* 6. I stop rTorrent, **move** all Downloads/some_dir **to offline storage**, free the space 7. much later somebody asks to share some_dir again (as no seeded is active) 8. I copy some_dir from offline to the box ~/torrents/Download/some_dir 9. **What now?** How to say rtorrent, to share it again under the original magnet?

I'm trying to compile [libtorrent](https://github.com/rakshasa/libtorrent) on Alpine Linux. autogen and configure work fine but after invoking make it fails with the following message: local_addr.cc:45:10: fatal error: linux/netlink.h: No such file or directory I looked in /usr/include and found only netlink/netlink.h. However the next include in the source file is rtnetlink.h which doesn't exist. Is this due to a missing dependency or perhaps a problem related to glibc/musl? How do you build libtorrent/rtorrent under Alpine Linux? I am aware there is an rtorrent package for Alpine but would rather prefer to build it myself, so I can customize the build options. These are the packages I installed prior to my build attempt: * autoconf * automake * libtool * pkgconfig * ncurses-dev * zlib-dev * libsigc++-dev * libcurl * curl-dev * libnl-dev

Searching for "move" and "rtorrent" only leads to questions about completed torrents. I'm interested in moving a single file that is part of a larger torrent to a different directory.

For testing purposes i even raised root's limit. # /etc/security/limits.conf * soft nofile 65535 * hard nofile 65535 root soft nofile 65535 root hard nofile 65535 rtorrent process is run by user "user". user@localhost:~$ ulimit -n 65535 But when i look up rtorrent's maximum number of open files: user@localhost:~$ cat /proc/1141/limits Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 8388608 unlimited bytes Max core file size 0 unlimited bytes Max resident set unlimited unlimited bytes Max processes 15700 15700 processes Max open files 1024 4096 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 15700 15700 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us I'm running Debian 9.1 Stretch. The max_open_files limit in .rtorrent.rc config is also set. I rebooted after the changes. Any idea why ? Thanks for your answers! **EDIT: Looks like screen is the reason. If i start rtorrent without screen, everthing is fine. Any idea why ?**

For quite some time, I've been fighting a problem with my Raspberry Pi having difficulty to maintain a connection to my external HDD. Sometimes it just randomly throws I/O error, and when that happens, my rtorrent service unit fails with it. Now I tried many things, this is the solution that I have now: [Unit] Description=rTorrent After=network.target [Service] User=root Type=forking KillMode=none ExecStartPre=/home/pi/mount_media.sh ExecStart=/usr/bin/screen -d -m -fa -S rtorrent /usr/bin/rtorrent ExecStop=/usr/bin/killall -w -s 2 /usr/bin/rtorrent WorkingDirectory=/home/pi Restart=on-failure [Install] WantedBy=default.target Where mount_media.sh simply remounts the directory. Stuff I also tried but didn't work: - OnFailure start different unit which remounts the directory - Start the unit with a script, which remounts the drive and then starts rtorrent Right now, this approach has left me with "cannot access 'Media': Transport endpoint is not connected" Forgot to add: /media/Media is my mount point So how should I take care of a moot point randomly disconnecting?

this one has been bugging me for a while and I cannot find any answer. In fact I usually get google results for cli torrent clients rather than what I want. So rtorrent is notorious about crashing when fed with magnet links. So to circumvent that I want to download torrent files directly from the command line. More often than not kickass torrents provide torrents of interest (f.e. slackware dvds) but by right clicking and "copy link location" will provide a link of the sort: > https://torcache.net/torrent/85922FBEE6DCE5E2F5491E16BCDD9E6E427BA5AA.torrent?title=[kat.cr]slackware64.14.2.iso If I wget this link, I'll receive a corrupt file named > "85922FBEE6DCE5E2F5491E16BCDD9E6E427BA5AA.torrent?title\=[kat.cr]slackware64.14.2.iso" which does not load in rtorrent correctly. curl also says: > curl: (3) [globbing] error: bad range specification after pos 86 Is there another command or some argument for curl or wget that I miss and which would correctly download the file? thank you

So there is a directory full of torrent files: debian.iso.torrent fedora.iso.torrent I can start downloading them with a: rtorrent *.torrent command, when the working directory is the same where the torrents are. But. Every time when I start rtorrent in this way it calculates all the hashes..it takes looong time do to that and it's a cpu intensive thing. Are there any methods to avoid this? (other console-based torrent client? or a feature to add a single torrent when already downloading a torrent without calculating all the torrent's hashes?)

I'm trying to setup xmlrpc-c with rTorrent but for some reason I failed: checking for XMLRPC-C... failed Here's my build script: output_dir=/home/world/apps curl -Lso - http://sourceforge.net/projects/xmlrpc-c/files/Xmlrpc-c%20Super%20Stable/1.25.24/xmlrpc-c-1.25.24.tgz/download | tar xzf - cd xmlrpc-c-1.25.24 ./configure --prefix=$output_dir make && make install cd .. curl -Lso - http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/libsigc++-2.2.10.tar.bz2 | tar xjf - cd libsigc++-2.2.10 ./configure --prefix=$output_dir make && make install export sigc_CFLAGS=-I$output_dir/include export sigc_LIBS=$output_dir/lib curl -Lso - http://libtorrent.rakshasa.no/downloads/libtorrent-0.13.3.tar.gz | tar xzf - cd libtorrent-0.13.3 ./configure --prefix=$output_dir make && make install cd .. export libtorrent_CFLAGS=-I$output_dir/include export libtorrent_LIBS=$output_dir/lib export PATH=$PATH:$output_dir/bin curl -Lso - http://libtorrent.rakshasa.no/downloads/rtorrent-0.9.3.tar.gz | tar xzf - cd rtorrent-0.9.3 ./configure --with-xmlrpc-c=$output_dir/bin/xmlrpc-c-config --prefix=$output_dir make && make install How come it' fails to check for XMLRPC-C?

My setup is the following: Physical host with QEMU/KVM -> VM with Docker -> rtorrent Docker container I have a ZFS pool called "main" with a dataset called "data". The "data" dataset is mounted on the VM via the virtio kernel module as suggested via this link . From here, my rtorrent Docker container has its download volume mapped to the mounted dataset on the VM: $ docker run -dt --name rtorrent-rutorrent --network=host -p 8080:80 -p 49160:49160/udp -p 49161:49161 -v /data/rtorrent:/downloads -e "NOIPV6=1" diameter/rtorrent-rutorrent:latest Here's where I'm confused: when I'm attached to the container, I can write to the dataset via touch, wget without issues. When I add a torrent to rtorrent however, nothing writes. It sits on "downloading" with no download speed. As soon as I change the container volume to point to the Docker VM local disk, everything works without issues. I've done a couple of straces on the rtorrent process (link here ) but there's not a whole lot that stands out to me here. Any input would be appreciated.

There is an option in rtorrent to report an IP to the tracker. I have a seeding rtorrent box connected to 4 WAN connections. I have configured port forwarding on all 4 wan connections and also made sure it is working. Now can i configure .rtorrent.rc file to report the tracker the IP's of all 4 WAN connections so that the peers can connect me via all lines ? I am doing this via an external load balancing and it doesn't support next hopping. I tried putting multiple 'IP' entries in the .rtorrent.rc file but rtorrent seems to read the last IP in that list.. perhaps overwriting the variable as it reads the file from top .. Any advice .. Thanks.

Is it somehow possible to disable upload in rtorrent? One would think that upload_rate = 0 might do the trick, but based on my tests and commented rtorrent.rc file in rtorrent source tarball, 0 is for unlimited speed. Or is *BitTorrent* protocol built in a way that at least some upload bandwidth is always required?