Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.3: Set the global umask default value' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.3: Set the global umask default value
Authored by: jethro on May 24, '04 05:48:02PM

HELP! I don't know where to look, but I'm having big probs with the whole sharing/permissions issue in Panther. We had it working great in Jaguar with a combination of the 'Global Umask' script and the program SharePoints.

I tried the hint above, and while it DOES seem to help permissions to be consistent when I write files to our shared drives (the shared drives are on my computer), when others (assigned to the group 'Staff') write or edit files to the shared drives, those users are assigned as the 'Owner' instead of Me.

The permissions for all files written by anyone (including myself - the administrator) need to be:
Owner: Me (administrator) - rw
Group: Staff (everyone else in the office) - rw
Others: r

So, as it is now, I cannot edit or write to any files put on the shared drives by anyone else. We NEED to be a collaborative environment. Please help!!



[ Reply to This | # ]
10.3: Set the global umask default value
Authored by: daniel_clift on Jun 14, '04 08:55:53PM

What you have written seems to suggest that you have only applied the umask fix to your machine (the server), and not those which your users are working from.

Although in your case you would also need to apply the fix to your "server" since you use it as your workstation, it is important to realise that the primary umask setting for a file is determined by the computer that saves it. The fix that Apple have implemented in Mac OS X Server 10.2.6 and above involves the server "overriding" this initial umask, essentially by creating a new file with the override privileges instead of those set by the individual workstation. In your more adhoc setup it is only really possible to solve the problem at source i.e. your users' computers.

That said, it might also be useful to check the SharePoint Preferences have been set to allow files in the shared directories to inherit their permissions from their parent directories, and maybe doing a quick sweep of those shared directories with BatChmod to correct any errant permissions.



[ Reply to This | # ]