If the hardlink creation fails or your setup does not support hardlinks then Lidarr will fall back and copy the file. The file system and mounts must be the same for your completed download directory and your media library. A hardlink will allow not use any additional disk space. When files are imported to your media folder Lidarr will hardlink the file if supported by your setup or copy if not hardlinks are not supported. Completed files are left in their original location to allow you to seed the file (ratio or time can be adjusted in the download client or from within Lidarr under the specific download client).This monitoring occurs via your download client's API. Lidarr will monitor your download clients active downloads that use that category name.If the "Completed Download Handling - Remove" option is enabled in Lidarr's settings leftover files from the download will be sent to your trash or recycling via a request to your client to delete/remove the release.If the the atomic move fails or your setup does not support hardlinks and atomic moves then Lidarr will fall back and copy the file then delete from the source which is IO intensive.
Atomic Moves (instant moves) are enabled by default.If it can do that, it will rename the file according to your specifications, and move it to the specified media location. It will parse the file name to match it against the requested media. Lidarr will scan that completed file location for files that Lidarr can use.This file location can be almost anywhere, as long as it is somewhere separate from your media folder and accessible by Lidarr When the download is completed, Lidarr will know the final file location as reported by your download client.
It monitors this via your download client's API.
0 kommentar(er)
