Re: [Netatalk-admins] Fwd: Struggling with Netatalk3 on FreeBSD/ZFS - cannot create files as other users.

[Dr J. K. <jo...@tr...>]

>> Am 09.02.2017 um 16:02 schrieb Dr Josef Karthauser <jo...@tr...>:
>> 
>> You’re right. user2 can connect and see the files so I don’t think that comma space is an issue.
>> (Just removed the space to confirm and it still doesn’t work).
>> 
>> I’ve enabled debug on all the logs, but there aren’t any particular error messages - probably because it’s the finder that’s complaining not the server. It doesn’t think that the user has write permissions.

> On 9 Feb 2017, at 15:15, ant...@ma... wrote:
> 
> Hmm, ok. I also get different permissions depending on the local file system:
> The top share ( as path in afp.conf ) has 755 as permissions, while the next level of directory 4775 and so down.
> So the top level of my directory is read only for every normal user also in that group ( and that is also visible in Finder) , while the next level than allows the user access through group ACL’s
> To make a long story short : have you verified your local file system permissions on the server ? So ls -d /data/test allows writes to user2 ?

The problem I seem to have is that with 775 on my top level (i.e. group writable), other members of the group can’t write, only the owner. This suggests that the unix file flags are not being translated into whatever MacOs wants to see. When I log in a user2, the finder says that the volume is readonly for (unknown), whereas when I log in as user1 the finder says that the volume is read/write for (unknown) - this is irrespective of the state of the ‘chmod’ed permissions on the root directory.

Joe