Documentation on systemd service about rtorrent HOT 2 OPEN

* after starting with tmux, there is no indication on how to access to the processus already started.

tmux a -t rtorrent There are lots of good resources for using both screen and tmux out there, e.g. https://tmuxcheatsheet.com/

* this one fails to start `socat[2028332.281473144643616] E symlink("/dev/pts/1", "/run/rtorrent/tty"): No such file or directory`

My guess would be that /run/rtorrent needs to be created first, but haven't tested it.

The wiki is publicly editable, I've added the thing you've mentioned, but feel free to update it yourself if you find anything else missing.

You may also want to consider using daemon mode (system.daemon.set = true in the rtorrent.rc) if you don't want the hassle of dealing with screen or tmux, at the expense of only being able to operate it via the XMLRPC API.

from rtorrent.

tmux a -t rtorrent There are lots of good resources for using both screen and tmux out there, e.g. https://tmuxcheatsheet.com/

Thanks. I edited your edit because it wasn't visible.

My guess would be that /run/rtorrent needs to be created first, but haven't tested it.

Not sure. /run is a in memory tree, thus any addition won't survive to a reboot. It should be a mechanism to create it, not by the user.

The wiki is publicly editable, I've added the thing you've mentioned, but feel free to update it yourself if you find anything else missing.

Done, a little space

You may also want to consider using daemon mode (system.daemon.set = true in the rtorrent.rc) if you don't want the hassle of dealing with screen or tmux, at the expense of only being able to operate it via the XMLRPC API.

I have considered it, but for now i'm stopped because this section is still void https://github.com/rakshasa/rtorrent/wiki/Daemon_Mode

from rtorrent.