OSX (Yosemite) file permissions on files written to SMB-shares

9,489

Solution 1

If the share is managed via the Server app, enable ACL's on the server, and configure the share through the Server app adding a group that all the team members are in and giving them read/write access.

I had a similar problem in the past and chmod/chown/chgrp simply didn't cut it.

edit: Forgot to mention you'll also need to enable inheritance permissions when setting this so that when new files are created, the same permissions are enabled on these files/folders.

Solution 2

You really should set it up on the server as it is the most correct way:

https://support.apple.com/en-gb/HT203574

That said, setting inheritable ACLs from a client is often possible.

Otherwise disabling UNIX extensions on all the OS X clients may work:

How to keep group-writeable shares on Samba with OSX clients?

Share:
9,489

Related videos on Youtube

Pim Jager
Author by

Pim Jager

Updated on September 18, 2022

Comments

  • Pim Jager
    Pim Jager almost 2 years

    In my workplace we work with a big SMB-share on which all files are saved.

    Files saved by windows machines by default have -rw-rw---- as permissions and all folders come with drwxrwx---.

    However the files written from OSX (Yosemite) machines have -rw--w----. This is a problem since it means that other team members can not view those files.

    Is it possible to set the default permission for files written by OSX on the SMB-share to 0660? Right now I fix this manually through the terminal everytime I write a file, but that leaves a lot of room for user error (i.e. forgetting to change the permission).

    I'm already running SMBUp, but sadly this has not fixed the issue.

    EDIT: preferably without changing serverside settings

  • Pim Jager
    Pim Jager about 9 years
    Ah yes, that could be an option. But I'd have to take that up with our IT-supplier. I would prefer to be able to do this without changing settings on the server.
  • Pim Jager
    Pim Jager about 9 years
    Thanks for you response, to bad it isn't possible to fix this client side.