Open KoenDeMol opened 1 year ago
@KoenDeMol Does this still apply to the latest version of ruTorrent (v4.2.*
)?
Regardless, I don't think this will be looked into any further given how simple it is to have workarounds for it. It's expected that when you setup ruTorrent, you would browse the GUI to setup everything. And if you have a backup, this would not happen I guess
Besides, you could simply setup a watch directory with rTorrent directly in .rtorrent.rc
if you don't want to use the GUI at all. Even with labels etc
schedule = watch_directory,1,5,"load.start=[WATCH_DIR]/*.torrent,d.directory.set=[DOWNLOAD_DIR],d.delete_tied=,d.set_custom1=[LABEL]"
Support guidelines
I've found a bug and checked that ...
Description
I did find some other posts on other forums, but none that brought me to the solution.
After reboot of the docker container, the plugins are not initialized. Even though the execute2 line is in .rtlocal.rc (as documentend), that script is never called (I added logging). Because of that plugins (like autotools, folder watch, .. ) are not started.
Expected behaviour
The execute2 line (in the .rtlocal.rc file) containing the initplugins script should run on start of the rtorrent service making autotools run (and watch folders) without having to browse to the GUI.
Actual behaviour
I have no idea why, but the execute2 line is not called. Might be an issue with (reading) the .rtlocal.rc file, or with the point and which execute2 is to be called. Anyways ... autotools is not running, files in the watch folders are not picked up.
Steps to reproduce
(What I also did:
Docker info
Version
docker-compose --version
):uname -a
):Linux NAS-FIT 5.10.60-qnap #1 SMP Fri Apr 21 00:44:05 CST 2023 x86_64 GNU/Linux
Docker compose
Container logs
N/A
Additional info
I tried numerous things, including but not limited to:
In the end, what did work for me:
But I guess that is really a workarround and not a solution.