Okay, jumped the gun asking for help. For some reason the launchd-user.conf file I created wasn’t displaying the .conf extension, even though it was shown on get info. Strange. Anyway after recreating the file it worked.
But now, I’m confused over what it’s doing:
I thought umask was only suppossed to restrict permissions but they would still be granted based on the enclosing folders permissions. Is this not correct?
Now with umask 002 set everything created in a folder with 700 permissions is created with 774. I know others won’t have access to the folder anyway, but it’s not how I thought it would behave.
Argh, this is driving me crazy,
This is not working for me. It works if I add “umask 002″ to /etc/launchd.conf, but obviously I don’t want that for all processes.
Can anyone think of why it wouldn’t be working in launchd-user.conf???
Okay, jumped the gun asking for help. For some reason the launchd-user.conf file I created wasn’t displaying the .conf extension, even though it was shown on get info. Strange. Anyway after recreating the file it worked.
But now, I’m confused over what it’s doing:
I thought umask was only suppossed to restrict permissions but they would still be granted based on the enclosing folders permissions. Is this not correct?
Now with umask 002 set everything created in a folder with 700 permissions is created with 774. I know others won’t have access to the folder anyway, but it’s not how I thought it would behave.
Any thoughts? Thanks.
The goal of this change is to allow users who share a mac to be able to create files/folders and have other users access them.