If you want to work with multiple users on the same files is one of the fast Permissions annoyed. While there is the folder "/ Users / user" (aka / Users / Shared), but this in no way ensures the correct access rights of files stored in it. The access rights must be the owner of a file in the worst case for each change manually readjust. Adjusting means for OS X to 10.3 allow the write and read access for all users (ie including guest accounts). An unsatisfactory solution.
The most obvious solution is now a joint group to access files to use. One could use eg the group "staff" (Eng. employees) or "wheel". To 10.2, new files by default, nor to this group memberships generated. "Staff" of files from regular users and "wheel" for admins. Since 10.3 The new files are created but with a group, the same name as the user's short name which they created. "Staff" and "wheel" are no longer used in favor of increased security and flexibility.
The "trick" is now as follows: Benutzerm who want to collaborate on files will be included in the group with the name of the other. So if two users with the name / group "dirk / dirk" and "tina / tina 'are so tina join the group and dirk dirk in the group tina. This alleviated the problem and you need only access rights to the group to jointly to work on a file. One might now fear that the users get this write or additional reading rights in the home directory (aka folder private) of the other user. This is not the case, as the group permissions are set by default as well as the rights of other users (such as the guest account). Ie for the sub-folder "Documents", "images", "Library" has by default only the owner has read and write, and the home directory itself can view anyway all users logged onto the system, which is why no private DCRT files should save.
To expand the group membership, you use the "NetInfo Manager". Furthermore, one should still take into consideration the sticky bit of the folder "Shared" (aka / Users / Shared) to delete, otherwise, only the owner of a file, delete it. Why this privilege is set by default is unclear to me.
| More info: | Apple Training Series: Mac OS X System Administration Reference, Volume 1 |
