Hey Everyone. I currently have a problem with permissions for Shared Folders on Mac Leopard Server. After creating a folder and sharing it, I assigned a certain group (from the Open Directory) read and write ACL permissions, and chose the inherit the permissions to child folders. I also made sure the permissions propagated. I created new folders inside the Shared Folder, but the permissions did not work properly. After fiddling around a bit, I noticed that POSIX permissions are messing up my ACL permissions. Unfortunately, POSIX permissions cannot be inherited, thus all inner folders should have their permissions manually edited. Also any new created folder will take the ACL permissions but won't take any POSIX permissions specified in the parent folder. Does anyone have a clue how to inherit POSIX permissions to child folders? Or have a fix or way to by pass the problem? Thanks you for your time :)
Shared Folder Permissions on Mac Leopard Servers
- Edited
Unix approach would be to open a terminal and type
Would love to get feedback from your experiment.
chmod -R <permissions> <filename>
The -R option makes it recursive. However, I had read somewhere that this is not recommended on Mac OS X. After all, they're trying to stay clear from the command line. A nice 'clean' utility could be BatchMod. Never used it, but it looks interesting. Would love to get feedback from your experiment.
uh...
chmod 777?
Lol
chmod 777?
Lol
Hey man. Tnx for your reply. I did use BatchMod and its an amazing GUI tool that does the chmod code on a selected file. Unfortunately, I still have the problem with newly created folders. When you apply BatchMod, only the existing folders are affected. Once you create a new folder, the new folder will not take the POSIX permissions of the parent folder, but ACL do. But since POSIX are dominent over ACL, then whatever permissions you assign to ACL, they will be limited to the POSIXrahmu wroteUnix approach would be to open a terminal and typeThe -r option makes it recursive. However, I had read somewhere that this is not recommended on Mac OS X. After all, they're trying to stay clear from the command line. A nice 'clean' utility could be BatchMod. Never used it, but it looks interesting.chmod -r <permissions> <filename>
Would love to get feedback from your experiment.
Only thing I can tell you is to try to go from the command line. I never had a Mac, so I don't know if it's bad, but if you need a quick and dirty solution, it'll do the trick.
NB: I edited a mistake I had done in my first post. it's '-R' not '-r'.
NB: I edited a mistake I had done in my first post. it's '-R' not '-r'.