Umask doesn’t change after reboot

permissionsmb

I'm new to umask so please correct me if i'm wrong.

We have a mac OS X file server at work with multiple SMB shares. Whenever users create files, they get created as -rw-r–r– as this is the default umask (022). I want to change it to (002) so created files will have -rw-rw—- as default. This way all users in the same group can access the files.

Apple advises to change umask like this:

sudo launchctl config user umask nnn

After doing sudo launchctl config user umask 002 I got the following message:

Configuration applied. You must reboot for changes to take effect.

I rebooted and got the following:

$ umask
0022

what am I doing wrong, please advise.

I'm running OS X Server 10.10.3 Yosemite with Server.app 4.1

Best Answer

I can only guess but I think it's an error in 10.10.3 which is solved in 10.10.5 (or maybe 10.10.4) because none of my 10.10.5 hosts show your 10.10.3 behavior.

So I recommend to update to 10.10.5/4.1.5.

BTW the integer in /var/db/com.apple.xpc.launchd/config/user.plist is calculated by converting the three binary "triplets" to a decimal number:

002 = 000 000 010 =   2
022 = 000 010 010 =  18
666 = 110 110 110 = 438

Related Solutions

MacOS – Confounded by permissions problem on NFS share

Your noowners mention solved all of my issues. I would make sure all of your options are being applied w/ nfsstat -m -- mount_nfs likes to remove / add options and not list them when you just type mount I also am using launchctl configuration that runs a mount_nfs command, since automount was being unpredictable. I do see an s (setuid/setgid) up there in the permissions... I'm using nosuid...

Here's my working mount_nfs line, you probably can remove some of the options (some are duplicates), but I feel better having all the variations for some reason ;)

 mount_nfs -o "vers=3,noowners,nolocks,nolockd,nolock,nonlm,automounted,nosuid,hard,bg,noresvport,intr,rw,tcp,nfc"       <server>:/exports/myexport /Volumes/myexport

From ls -l from /Volumes:

drwxrwrwx  13 larry  staff   4.0K Jan 17 17:37 myexport

All folders within myexport are drwxrwrwx as well.

It's been an ongoing battle to get NFS and OSX working together but when it works it works flawlessly and fast. AFP is on the way out, and Apple is sticking with Samba, which has always been a pain in my neck, whether the clients are OSX or Windows, there was always some sort of issue.

MacOS – Mount network share (AFP/SMB) for multiple users (fast user switching)

Setup your NAS to export a NFS-share. Refer to the Synology knowledgebase how to do this or use the following how-to to set it up, fine tune and secure your set-up.

You may do it manually in the command line also:
Let's assume your media folder is /Shares/Media. Create or edit a file named exports in /etc. The example below restricts the access to computers with an IP address in the range 192.168.0.1 - 192.168.0.254. You may have to restart your NAS or at least nfsd (nfs-daemon).

Linux/NAS file /etc/exports:
```
/Shares/Media 192.168.0.0/255.255.255.0(rw)
```
if you use a Mac Server use this line:
```
/Shares/Media -network 192.168.0.0 -mask 255.255.255.0
```

Edit /etc/auto_master on your Mac and add the line:

/-                                  auto_media

file /etc/auto_master:

#
# Automounter master map
#
+auto_master                        # Use directory service
/-                                  auto_media
/net                                -hosts      -nobrowse,hidefromfinder,nosuid
/home                               auto_home   -nobrowse,hidefromfinder
/Network/Servers                    -fstab
/-                                  -static

and create a new file auto_media in /etc on your Mac

file /etc/auto_media:
```
/Media         IP-NAS:/Shares/Media
```
Please don't forget: all files mentioned above need a trailing empty line

enter sudo automount -vc in Terminal on your Mac with the output:

$ sudo automount -vc
automount: /Media updated  
automount: /net updated  
automount: /home updated  
automount: no unmounts

/Media will now always be visible in the root folder of your Mac and accessible for both of you as long as the NAS is up & running. No Apple Script to mount it nor a Connect to Server needed.

(Set up and tested on a Server 10.7 (no Synology NAS, because i don't own one, but it shouldn't make a difference) and Client 10.9)

Best Answer

Related Solutions

MacOS – Confounded by permissions problem on NFS share

MacOS – Mount network share (AFP/SMB) for multiple users (fast user switching)

Related Question