I apparently wrongly assumed that choosing the hardlinks option for imports would not delete the original file. I never want that file deleted as it it continues seeding indefinitely. Presumably this is done so that Sonarr does not continually try to import the same file.
Am I correct in assuming there is no solution for this in-app? I suppose I can create a hardlink inside a ‘staging’ folder myself post download that can be the new import directory.
Hardlinks are only used if Sonarr is able to communicate to your download client and the file is still seeding, if you’re using Drone Factory or the file is stopped in your download client Sonarr will move the file.
Oh that’s great news, must be a bug then. I am using transmission to which Sonarr communicates properly and the file never stops seeding. So far every other feature of the app works flawlessly, including adding downloads to Transmission.
Are you using the Drone Factory with transmission? If Sonarr is connecting to the Transmission API directly it will get the path from it so it doesn’t matter where the script hardlinks it to.
Please use hastebin.com and post a few minutes of ((trace logs)) so we can see the full output, clear your log files before you set it to trace and they shouldn’t full of other noise.
I am, but I noticed the option to handle completed downloads. I’ll grab trace too, but in the meantime I disabled that so Sonarr is only looking at the processed directory. Thanks for the heads up on that.
Not entirely sure what you disabled, but disable Drone Factory and change its path, it doesn’t ever copy or hardlink, only Completed Download Handling will when it takes to Transmission. If the path Transmission reports and Drone Factory is set to are the same partial path the Drone Factory will be used.