[X] ... the documentation does not mention anything about my problem
[X] ... there are no open or closed issues that are related to my problem
Description
Cross-seed works by symlinking a torrent's files to a directory and then sending rTorrent a torrent file with the symlinked copy as the new torrent's save path. I believe that the directory.default.set designation in .rtlocal.rc is preventing cross-seed from being able to set the torrent's save path on injection.
Expected behaviour
I expect to be able to take control over my config if necessary.
Actual behaviour
When I edit .rtlocal.rc any changes are reverted as soon as rTorrent starts. I've tried setting the file as read-only but then the process fails during startup. I cannot find any other way to unset directory.default.set
Steps to reproduce
Mount /etc/rtorrent/.rtlocal.rc to a path on docker host
Attempt to modify .rtlocal.rc
Start container
File has been reverted back to a clean copy
Start a search with cross-seed
Injected files have save path of /downloads/temp instead of the one designated by cross-seed
Support guidelines
I've found a bug and checked that ...
Description
Cross-seed works by symlinking a torrent's files to a directory and then sending rTorrent a torrent file with the symlinked copy as the new torrent's save path. I believe that the
directory.default.set
designation in.rtlocal.rc
is preventing cross-seed from being able to set the torrent's save path on injection.Expected behaviour
I expect to be able to take control over my config if necessary.
Actual behaviour
When I edit
.rtlocal.rc
any changes are reverted as soon as rTorrent starts. I've tried setting the file as read-only but then the process fails during startup. I cannot find any other way to unsetdirectory.default.set
Steps to reproduce
/etc/rtorrent/.rtlocal.rc
to a path on docker host.rtlocal.rc
/downloads/temp
instead of the one designated by cross-seedDocker info
Docker Compose config
Logs
Additional info
No response