-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deluge file permissions! #1960
Comments
Deluge doesn't provide the functionality to set (unix-type) permissions. We can't work around that due to other limitations, for example: umask doesn't work with busybox's start-stop-daemon (at least, not as far as I know). However, instead of relying on unix permissions, we can use the ACL functionality Synology provides. Similarly, integration with other SynoCommunity packages (Sonarr, SickRage etc) can be done by setting rw permissions for the |
Closing. If my explanation isn't clear, or you still run into issues, let us know. |
It was clear. But no matter what I did it did not change the permissions from 755. It is not an issue with transmission or rutorrent. So this is not a synology issue but a deluge issue. Although I dislike the work around I changed the deluge user and sickbeard user to root so they are considered the same account which has resolved the issue for now technically |
My point is, you don't need to change the unix permissions...or at least, I haven't found a reason to do so. |
Could you please describe in detail how to make this work? I am a bit lost. My problem is that couchpotato cannot seem to unrar the files. The couchpotato user is part of the "users" group. I guess the problem is the group doesn't have write permission inside the downloaded folder. |
Thank you for your explanation @Dr-Bean but I too am stuck with this. Anything downloaded with deluge appears unable to be automatically or manually post-processed by sickrage (Files downloaded by deluge have permissions 644 and are owned by deluge in group users). An example of a file able to be processed by sickrage on my nas is something downloaded by SABnzb (files here have permissions 666 and are owned by sabnzbd in group usere). I took your point about using ACL and this is what I did to change perms (just checking that I've done the right thing and also to help @kamakamadaun ):
Is that a long-winded way of describing what you said above, @Dr-Bean ? If so, then I have completed these steps and still am unable to post-process deluge files correctly. One thought is that, are ACL permissions assigned to the files at the point of the file's creation or are they assigned to the file at the point where perms are updated in the UI. I had assumed it was the latter as that would make most sense(!) ...in which case I don't understand why is this still not working? |
Just to follow this up, after I failed to set the ACL-based permissions I tried various linux permission changes to the files to get them to process automatically - none of which worked. I then moved up the directory tree to try to make a difference. Many of the individual downloads create their own directories and by changing the ownership of these to sickbeard-custom in group users I was able to get them to auto-process. Changing the group to sc-media made no difference. Does any of this explain why the ACL permission changes aren't doing what I think they should? |
I solved this by wrapping deluged with a small shell script. |
@alonalbert. I have the same problem but no idea to do this can you help? |
Deluge makes 755 file permissions when downloading and after completing. I would assume a 775 would be more accurate as group permissions would be assumed... If that is not the case how do i change?
thanks!
The text was updated successfully, but these errors were encountered: