osx - Single permission OS X ACL entries

06
2014-04
  • Adam

    I'm just trying to understand what happens when you apply a new ACL entry (specifying only a single permission) to a directory or file through the terminal.

    For example if I were to run this to allow write access for all users in the developers group for all the found files and directories in the current directory:

    sudo find . -exec chmod +a "developers allow write"

    Would that then use a set of defaults to determine whether the user is able to say list the files in a directory, or would it fall back to checking against the traditional POSIX execute permission?

    • Answers
  • Adam

    An action, say listing the files, only uses the ACL if you have specifically defined that permission as either allow or deny. Otherwise the normal POSIX permissions are used.

    Thinking back I don't know why I didn't click on to that, it makes perfect sense.


    • Related Question

    permissions - How can I get vim to set an ACL on its swap files?
  • thsutton

    I use vim on an OS X Snow Leopard Server machine. A number of the directories I work in have ACLs (so that various groups of users can access them over AFP) that are inherited. For some reason, when I'm working in one of these directories, vim cannot read it's own swap files. It can create them fine but can't read them which, for some reason, makes it display the "swap file already exists" message (and no, the swap file does not already exist).

    vim -r lists the newly created swap file as "[cannot be read]". The owner and group are correct and the permissions are 0600, and the ACLs on the swap file and the file I'm editing are identical (as disclosed by ls -le and compared with diff). groups returns the same thing whether invoked from my login shell or via :! in vim.

    Has anyone encountered (and hopefully resolved) a problem like this before?


    • Related Answers
  • akira

    create the swap files in a folder you own.

    :help directory