this post was submitted on 02 May 2025
294 points (99.0% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
62408 readers
307 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
🏴☠️ Other communities
FUCK ADOBE!
Torrenting/P2P:
Gaming:
💰 Please help cover server costs.
![]() |
![]() |
---|---|
Ko-fi | Liberapay |
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You see, the problem is that radar and sonarr move my files into designated folders. That is a good thing, but it also makes it so that my download client can't find it again to continue uploading.
I have now set it up so that I keep a copy in my downloads folder for a week, but I don't have the space to permanently keep two copies of all my downloads.
It would be great if radarr could tell my download client where the file has moved to so that it can keep on seeding indefinitely.
You can configure radarr and sonarr to use hard linking instead of moving the.
Yes, but hardlinking doesn't work if the files aren't on the same petition.
My downloads folder is on the main harddisk.
The files are moved to an external ssd.
Have you looked into Remote Path mappings? I have not had to employ this myself, but my understanding is this allows you to avoid file duplication when your *arr and torrent client are using different filesystems.
Maybe I'm mis-remembering though...
I will look in to that