![]() (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. It does not affect your data or settings in any way and is completely safe to do.TL DR - Check the permissions on your remote share, too. Restarting Finder is a common troubleshooting step recommended by Apple to fix various issues. It’s perfectly okay to relaunch Finder on a Mac. If none of these steps work, you may want to contact Apple Support for further assistance. To do this, click on the Apple logo in the top left corner of the screen, select “System Preferences” from the dropdown menu, and then click on “Software Update.” If an update is available, click the “Update Now” button to install it.īy following these steps, you should be able to fix most issues related to Finder not responding on your Mac. Check for updates: If restarting Finder and your Mac don’t work, the next step is to check for updates to macOS.Wait for your Mac to restart, and then check if Finder is responding properly. To do this, click on the Apple logo in the top left corner of the screen and select “Restart” from the dropdown menu. ![]()
0 Comments
Leave a Reply. |