MacOS – What does it mean to have “custom access”

macossmb

I'm having some permissions-related trouble with OSX clients and a Samba server.

When I create, for example, a new directory on the mounted share, it will be created with rwxr-xr-x permissions. But when I open the info window for the directory in Finder, it will tell me "You have custom access" and it won't allow me to display or change the permissions for the directory.

What is the message trying to tell me and why won't Finder let me change the permissions?

Best Answer

Generally, the "You have custom access" can indicate that the file has more complex permissions set than the Finder's Get Info window can display. From this Apple support article:

Custom: If the permissions for an item is set to Custom, the permissions have been configured in a way that is more complex than is provided in the basic user settings.

It's possible that the files on your SMB server have Access Control Lists setup. You may be able to get additional information about these (non-POSIX) permissions in OS X by using a command like ls -ale /Path/To/Folder.

It's probably also worth noting that the Finder may have problems setting permissions on your SMB share. I'd probably recommend configuring some sort of server-side permissions inheritance (i.e., using ACLs) to keep permissions in check on your share.

Related Solutions

Dot-files and other meta data on non-Mac network shares

Is the file you're trying to copy using a resource fork?

If you're dealing with .DS_Store file issues run the following command in Terminal:

defaults write com.apple.desktopservices DSDontWriteNetworkStores true

If you're having issues with resource forks on Snow Leopard you may need to change your settings for the streams setting in smb.conf on the Linux machine or nsmb.conf on your local Mac. (._FILENAME files are the resource forks of the file). Check out Super User for more details on this.

Network disconnect causes leftover directory under /Volumes

Not an answer, just to let you know that I cannot emulate your problem in a similar setup, and that you might have a problem.

I have an iMac with 10.6.8 and a MacBook with 10.8.1. Sometimes I forget to eject the connected volume on the iMac before I shut down the MacBook, and then the mounted volume remains as an image on the Desktop and in the sidebar of any open folder. I then simply click the eject-symbol in the folder sidebar or right-click on the desktop symbol and tell finder to eject the volume. It disappears. Now, looking in my /Volumes (in Finder as well as in Terminal), there is no remaining network volume. Maybe ejecting it did the trick.

Now, if I do NOT eject the remaining volume after I shut down the MacBook (or put it to sleep) and then boot (or wake) it and connect it again, the remaining volume icon on the desktop disappears and a new one appears. If I check under /Volumes (in Finder and Terminal), there is only one connected volume. (I did not shut down the iMac or do anything, except shut down the MacBook and start it (or put it to sleep and wake it) and connect it again.)

I do not get a Finder notification, that the drive is no longer available, either. If I try and access the disconnected drive by double clicking on the icon on the desktop, I can even browse its contents, until it automatically disappears when I reach I point where I have not been during this connection (open a subfolder that has not yet been opened).

Best Answer

Related Solutions

Dot-files and other meta data on non-Mac network shares

Network disconnect causes leftover directory under /Volumes

Related Question