Benches macOS

2

umask keeps getting reset to 0022 (Leopar…

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Hi, I need to have my umask set to 0002 for file sharing purposes. I can go into Terminal and change it from the default 0022, which I can verify immediately afterwards by just typing "umask" and creating new folders and files, which have user and group read+write access as they should. So far, so good. But Leopard keeps periodically resetting it to 0022. This happens on reboots but also just every now and then while logged in (I can't find what's triggering this). This is causing all kinds of annoying permissions problems for me because all our privileges are based on group access, so no one can access any files I create after Leopard mysteriously resets my umask.

This is happening on multiple machines, including a quadcore Mac Pro, a new iMac, and a MacBook Pro, all running 10.5.4. I had suspected .Mac/Mobile Me syncing as the culprit, but I've turned that off and it's still doing it with no syncing happening. I'm not running any daemons or background processes that I know of which would do something like this, does anyone have an idea what causes it, or how to fix it?

2 replies

Sign in or join Beachball Help to reply.

  1. 0

    madconqueror

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    What protocol do you use?

    Have you tried ACLs (inherit) or can't your clients read them?

    --greg

  2. 0

    V.K.

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    you might try using inherited ACLs as the other poster suggests.

    changing umask is tricky in leopard. first, that terminal command only changes umask in the shell. it has no effect on any GUI applications including finder. I couldn't find a way to change umask on per user basis but you can change it for all users as follows.

    1. Create a new file in /etc called launchd-user.conf. Add the following line:

    umask 002

    2. Reboot

    After logging in, you'll see that your umask from the command line is 002, and files saved through GUI applications also seem to save using that umask.

    Use this at your own risk. this feature is undocumented.