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
Transmission permission issue on DSM5.0beta #827
Comments
The transmission SPK doesn't create any share. What are the permissions on the folder? |
I mean, created shared folder myself. |
I think Synology changed things up with default shared folder permissions. DSM5.0 permissions are set to 755, whereas DSM4.3 permissions are set to 777. Might be easiest to add a |
Has anyone fixed this, im having the permission issue myself |
If this is a DSM 5.0 bug, then it should be fixed, if not, we'll implement a fix. |
@Diaoul It seems Synology did this "on purpose" when implementing ACL to limit the default permissions on directories. There are two ways to solve this that I can think of: Solving it via the ACLs means creating users with If not via the ACLs, it's either chmodding or chowning the dir to enable access to the user (or maybe a synocommunity group?). NZBGet, SAB, Transmission are the main packages which will be affected by this (only with clean install on DSM5: when upgrading from 4.3, 777 permissions are retained on shared folders) |
So, looked into it a bit: @Diaoul, did you ever get a response from Synology on the subject? |
Synology confirmed this is a feature not a bug so we need to fix this in a way. I'm against using non-system users as the ACL settings won't work anyway (well at least it didn't work last time I tried, this is pure UNIX permission issue, no DSM layer involved AFAIK) and it adds complexity to the packages. The issue is that the |
ACL doesn't seem a viable option, no, and if we keep away from DSM, that's all the better. I was checking your fix, and there might be a minor catch: A freshly created shared folder is owned by root:root, so we'll have to Besides that, I did notice some packages use the |
Just ran in to this issue on a new ds214play with DSM 5.0. Is there a quick fix with chmod or so to fix the problem? I tried setting my downloads path to 777 but no luck. Files are not created. Edit: I solved the problem temporarily by /volume1/transmission to 777 only changed /volume1/transmission/download before. |
Hello guys, I hope I can solve this problem for you. So what I did seems quite simple.
After I did this, everything seems to be working again. Screenshot included, but only in German. |
Thanks, although 8c5f37f should take care of it without having to do manual actions. |
Anyone know when to expect the new package to be released? |
Hopefully, next week, unless someone beats me to it. |
Great! :) |
The new Transmission package has been released in the SynoCommunity repository, along with an update to the latest Transmission version. When doing a fresh installation, the necessary permissions should be set correctly. Permissions are not changed when doing an upgrade of a previous package. So, closing as resolved. |
Hi, I would like to set my destinations folders in an external HDD (/VolumeUSB1/usbshare/...) but there is the same issue with permissions (even if I've done DS214Play Could you help me with that ? |
Hi, I use a similar configuration like mcobra an run into the same permission problems. Is this problem actually solved? DS414 |
File Station > Right Click (Share) Tab > [button] Create > User or Group (Everyone) .. (ok button) seemed to work for me .. user did not |
Yes, that's a nice work around but this not is practical is in a multiuser environment :| |
There's a permission issue that created share folder with DSM5.0.
It is normal created share folder with DSM4.3.
The text was updated successfully, but these errors were encountered: