![]() ![]() Regardless of the fact that these were beta releases, I have had this issue before. I had this same issue with a shared volume on OS X Server 5.1 under OS X 10.11.4 beta. (So AFP-running as admin-isn't in the group allaccount.)Īdd him to the allaccount group and voila, a happy Mac.Īloha. (Here, "baz" works everywhere, but "foo" and "bar" only work on my Windows machine.) $ sudo cat /etc/group (So Samba's running as root, but AFP is running as "admin".) $ cd /mnt/mysharesĭrwxr-x- 6 nobody allaccou 4096 Jun 25 02:50 fooĭrwxr-x- 11 nobody allaccou 4096 Jun 10 20:39 barĭrwxr-xr-x 12 nobody allaccou 4096 Jun 24 23:18 baz $ ssh myremoteserverĢ4642 admin 23680 S /usr/sbin/afpd -d -F /etc/netatalk/afp.conf Thus my Windows machine ran fine, and my Mac client seemed "buggy". When other clients, such as my Windows machine accessed the share, they accessed it via Samba ( smbd), which was running as root. But the afpd (Apple File Protocol Daemon) process wasn't in the group! So it was unable to access the files. They had 750 permissions, which seemed reasonable since I only wanted the owner and appropriate groups to get access to the folders. Long version - My issue was not with my Mac, but with the remote shares. Make sure the Samba daemon and the AFP daemon have access to the shares. TL DR - Check the permissions on your remote share, too. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |