Symlinks created as read only in Unraid

[vanreek]

NZBDav running in unraid from an app template.

Completed downloads go into designated directory, files become read only and do not inherit permissions from the parent folder.

[nzbdav-dev]

Everything in the webdav is readonly. There are a few exceptions:

• You can create or upload *.nzbs onto the /nzbs folder to add them to the queue.
• You can delete *.nzbs from the /nzbs folder to remove them from the queue.
• You can delete files from /content folder if you don't want them there anymore
  • Note: This may break symlinks that point to those files. Be certain before deleting.
  • You can only do this if NzbDAV -> Settings -> WebDAV -> Enforce Read-Only is not checked.

---

All other operations on the webdav are forbidden. You cannot create files, rename files, move files, or delete files, except for the exceptions above. Future updates will allow renaming and moving files, but it is currently not possible.

The symlinks are created on the webdav within the /completed-symlinks folder. Rclone is then responsible for making them available as if they were local to your filesystem (e.g. at /mnt/nzbdav/completed-symlinks). Radarr/Sonarr are then responsible for copying those symlinks to wherever you keep your organized media library (the "Root Folders" configured in Radarr/Sonarr).

So yes. the /completed-symlnks folder is read-only, since it exists in the webdav and the webdav is readonly. But Radarr/Sonarr should have no problem copying those symlinks (a read operation) to your Root Folders / organized media library.

[nzbdav-dev]

Note: Converting to discussion, since it does not appear to be an issue.