[[Support] binhex - rTorrentVPN]

More of a usage question about rtorrent, but it was this docker image that prompted me to try this:

 

I have about 5000 (linux) isos I thought I'd help seed - they're on a massive RAID volume and all hash-checked and verified.  I added this volume "/linux" as an additional mount into the docker container, and had the bright idea to make it a readonly mount to protect all that data from any mishaps on the docker container side.

 

It seems rtorrent won't allow me to seed off a read-only file system.  I tried the "d.seed_only" flag for the relevant torrents but that didn't help, when I tried to start them it failed with the read-only filesystem log error.

 

Note this isn't any problem with config files, they are all on the regular RW "/config" area and all my other torrents in "/data" are working fine.

 

I've successfully seeded off read-only filesystems with other torrent software before (eg deluge), but can't seem to find any work-around to make rtorrent do this.  Which is a shame as the docker setup makes it really easy to provide this protection.

 

Anyone else managed to tweak rtorrent to seed from a read-only filesystem?

 

 

[[Support] binhex - rTorrentVPN]

First off, thanks binhex for an incredible tool.  I'm a newbie to this image, and in the process of moving a lot of my stuff over.  If I find some stumbling blocks along the way hopefully my questions will help others.

 

First up, in "https://github.com/binhex/arch-rtorrentvpn/blob/master/README.md", section about "AirVPN provider" in the bit: about modifying rtorrent.rc to change the ports:

network.port_range.set = 20479-20479
port_random = no

 in the latest config file included with the image I noticed the following already exists:

# Start opening ports at a random position within the port range.
#
network.port_random.set = no

 

Are the "network.port_random.set" and "port_random" the same thing?  If so maybe the bit about port_random can be removed from the readme to make things even simpler using the latest image.

 

Second, I'm trying Pyroscope for the first time.  I searched for some guidance in this thread but most people commenting on Pyroscope seem to be old hands.  After a bit of digging around in the image I figured out pyroscope is already installed, but if you want the extra fields (loaded,completed,leechtime,seedtime) to work you need to add the config below to rtorrent.rc, as documented  at:

 

https://pyrocore.readthedocs.io/en/latest/setup.html

 

#
# PyroScope SETTINGS
#

# `system.has` polyfill (the "false=" silences the `catch` command, in rTorrent-PS)
catch = {"false=", "method.redirect=system.has,false"}

# Set "pyro.extended" to 1 to activate rTorrent-PS features!
# (the automatic way used here only works with rTorrent-PS builds after 2018-05-30)
method.insert = pyro.extended, const|value, (system.has, rtorrent-ps)

# Set "pyro.bin_dir" to the "bin" directory where you installed the pyrocore tools!
# Make sure you end it with a "/"; if this is left empty, then the shell's path is searched.
method.insert = pyro.bin_dir, string|const,

# Remove the ".default" if you want to change something (else your changes
# get over-written on update, when you put them into ``*.default`` files).
import = ~/.pyroscope/rtorrent-pyro.rc.default

# TORQUE: Daemon watchdog schedule
# Must be activated by touching the "~/.pyroscope/run/pyrotorque" file!
# Set the second argument to "-v" or "-q" to change log verbosity.
schedule = pyro_watchdog,30,300,"pyro.watchdog=~/.pyroscope,"

Hopefully the next time someone searches for Pyroscope in this thread this will save them some time.

 

Thanks again binhex.