This happens on the clients despite verifying that the permissions are set correctly as I have outlined them above. So the issue I see at this point is that sometimes the permissions are being ignored, and the users see erroneous error messages about not having proper permissions to affect files. I have no idea why the stripping and replacing with the exact SAME permissions they had before (at least with the ACLs) works. This tends allow most things to function normally for a time, but I eventually get a few complaints here and there until the problem becomes very common again and I am back to the reset route.
When the problem becomes a very common occurrence, what I do to mitigate the nightmare is to strip the ACLs from the shares and all child folders about twice a month and then set the posix permissions to 777 in Terminal.Then I go back to the Server App, and set things up as 775 again and then add in my ACL's and then finally propagate. While this behavior is WAY more common on the El Crapitan clients, it does also happen on Yosemite. If I try to fix it on the server end by modifying the permissions, that will sometimes allow the clients to then modify or delete the files, but in many cases, only a restart of the client computer will clear the problem, and in some cases, I have to move or delete the file on the server end. It seems that the clients are at that point ignoring the ACLs and relying solely on POSIX in these cases. However, when things go wrong nothing a local user does ever works. Even so, most of the time, the ACLS are respected regardless of the POSIX and the user has proper permissions. They always have "custom access" when viewed from the Get Info panel on the local computer. When users create a new file or folder they have a default umask of 022 regardless of the fact that I have set them to 002 (which is another thing that drives me nuts - why Apple why), and the ACLs are set correctly, but some times other clients cannot modify the files or delete them. I have set the permissions to propagate to all of the child folders and files. I have corresponding ACLs for the same admin user and the named staff group set to read and write. For permissions I have set the POSIX to 770, with the "everyone" bit set to no access. I have the shares using the local administrator of the server as the owner and the company's named staff group (which I created) as the POSIX group. Everyone is connecting to the server via SMB and using a number of shares that using POSIX and ACLs for permissions.
#Smbup no write permission full
I have a customer with a Yosemite 10.10.5 server (running on a 4,1 Mac Pro with a RAID system) and a whole office full of 10.10.5 clients mixed with 5 newer El Crapitan clients (which is extremely buggy, but I digress). I am also calling Apple support, which I don't think will make any difference, but I am hitting a brick wall, so I need to do something. I know this issue has been rehashed and posted in various ways over the years, but I wanted to put out my experience and specific circumstances to the community.
0 kommentar(er)
