Solved

File Sharing Permissions in OS X

Posted on 2007-11-19
2
3,621 Views
Last Modified: 2013-11-12
I am logged in to my G5 Mac Pro (running Leopard 10.5.1) as user 'ecAdmin'. This user is an Administrator.

I want to:

- Create a folder called 'ecShare' and enable file sharing

- UserA, UserB and UserC (three different users) should be able to connect to this computer (from their Macs) and mount the shared folder 'ecShare' on their desktops. I want them to log in with their own user name (in other words, I do NOT want them to log in as user 'ecAdmin')

- EACH user should have FULL CONTROL (read and write) to ALL files and folders in the 'ecShare' folder, regardless of who created the file or folder.

So, from my Mac, I create a folder called 'ecShare' and set permissions to:
  ecAdmin (Me) - Read & Write
  staff - Read & Write
  everyone - Read & Write

Next, I open System Preferences | Sharing and turn on 'File Sharing'

Next, I click the '+' icon to add a shared folder. I browse to my 'ecShare' folder and set the same permissions:
  ecAdmin (Me) - Read & Write
  staff - Read & Write
  everyone - Read & Write

So far so good, right? Wrong!

The second I create a file or folder inside of 'ecShare', I become the owner, but everyone else gets READ ONLY permission.

What gives? Why don't new files or folders inherit the permissions set by the 'ecShare' folder?
0
Comment
Question by:ecarbone
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 40

Accepted Solution

by:
Eoin OSullivan earned 250 total points
ID: 20318652
ecarbone - This is the DEFAULT behaviour of OSX.  All new folders are set as Read-only for Groups and others.
The article below discusses all the ways the get around this problem ... from easy to more complex.  
Personally I like the SharePoint Option discussed in Option 4 for Client Computers.

http://www.codebase.ca/art/index.cgi/OS%20X/OSX_Workflow_Perms.html

0
 

Expert Comment

by:jennixchange
ID: 25359439
Actually, none of the suggestions on the link above is valid for the user's question. In the time since the question was posted Leopard has been released (under which SharePoints does not function), and the option has also been removed from recent OSX server versions in favor of ACL's, which are unavailable under non-server versions of OSX.

Saying "this is the default behavior for OSX" neither solves his problem, nor does it make the issue a "feature" and not a bug as the article says.
Default behavior is one thing, but not giving ANY support for such a basic necessity in file sharing is just inexcusable.

The correct solution has been (finally) documented by Apple, and can be found here.

http://support.apple.com/kb/HT2202

I'll save you a click by reposting the meaty part:


Umask for user applications
In Mac OS X 10.5.3 and later, you can create the file /etc/launchd-user.conf with the contents "umask nnn". Do not include the quotation marks and replace nnn with the desired umask value, such as 027 or 002.
 
This will set the users umask for all applications they launch, such as Finder, TextEdit, or Final Cut Pro, and control the permissions set on new files created by any of these applications.
 
Umask for system processes
In Mac OS X 10.4 and later, create the file /etc/launchd.conf with the contents "umask nnn". Do not include the quotation marks and replace nnn with the desired umask value, such as 027 or 002.
 
This will set the umask for all processes. Changing this value is strongly discouraged because it changes the permissions on files used by the system software. If the permissions are too restrictive, dependent software may not work. If the permissions are too open, they may introduce security issues.
 
 
Umask for a specific LaunchAgent or LaunchDaemon
In Mac OS X 10.4 and later, advanced administrators can set a separate umask for a specific LaunchAgent or LaunchDaemon by adding a Umask value to the launchd plist file. This setting will override, for that process only, the umask setting in /etc/launchd.conf or /etc/launchd-user.conf. For more information on this option, see man launchd.plist.

Open in new window

0

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

An introduction to the wonderful sport of Scam Baiting.  Learn how to help fight scammers by beating them at their own game. This great pass time helps the world, while providing an endless source of entertainment. Enjoy!
This article outlines the struggles that Macs encounter in Windows-dominated workplace environments – and what Mac users can do to improve their network connectivity and remain productive.
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…

626 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question