Terminal vs. Server Admin: equivalent “Propagate Permissions”

[dr3do]

Hi folks

Since a while, but till now without luck, I’m searching for an equivalent CLI command to propagte the existing permissions like in the Server Admin GUI. Id like to run a script, without the need to start Server Admin and do it by hand (like a stupid).

May anyone help me? 🙄

Cheers,
dr3do

BTW: I’m not a native speaker, so please be forbearing with my mistakes. I’m working on it. 😉

[kcartini]

I’d like to second this request. I’m pretty much set with scripts for all the repetitive work I have to do, except for this. Not being able to script Server Admin is a real pain, so an alternative idea for automation of the permissions propagation would be appreciated.

kcartini

[kcartini]

Still no one? The problem we’re inquiring about seems to be so obvious, that one would think, someone has encountered it and already found a solution for it. Or is the solution TOO obvious? If that’s the case, I would still be thankful for a pointer in the right direction for more investigation.

Cheers,
kcartini

[kcartini]

Thanks for the pointer, macshome. Could you give me another hint, where to look for a generated script? And what did you do to find out, that Server Admin actually creates a script?

OS X Server is pretty easy to set up, which is good, but at the same time, it attracts total beginners like myself to set up a server and pop up in forums like afp548, asking basic questions. Sorry for wasting your guys’ time, but I’m always grateful for some help.

[jvickers]

[quote]Thanks for the pointer, macshome. Could you give me another hint, where to look for a generated script? And what did you do to find out, that Server Admin actually creates a script?[/quote]

As long as we’re seconding things, I’d like to second this request. 😛

I’ve actually just read through Josh Wisenbaker’s “Mac OS X Filesystem ACLs” whitepage, and learned a few things about Apple’s version of ACLs that appear to be slightly different from the *nix paradigm, much to my frustration.

I had just written a script that allows the user (me) to apply ACLs to all the folders in our file structure by using a provided excel sheet that will create chmod commands based on the user’s input. The idea being that we can use this same excel sheet for the existing folder structures of our different offices, without spending the time at the WGM to individually add ACLs. I noticed some funny things when I ran it (on a test volume, of course), however, that made me think twice. When I added entries such as “read”,”write”,”execute”, and “append”, I [i]wasn’t able to see the user’s permissions in the Effective Permissions Inspector.[/i]

I now know that those are added somewhat differently. I have run a few more tests, and I can see that running a recursive chmod command will add the correct “read”,”write”,”execute”, and “append” permissions to a file when I add the List, Traverse, Create Files, and Create Folders permissions to the containing folder. It’s sort of counter-intuitive if you’ve just been looking at ACLs on the CLI side, but if it works, I’m okay with it.

This means that I can change my “chmod +a ‘user allow permission'” command to a recursive “chmod -R +a ‘user allow permission'” command and fake propagation.
This is how I am proposing to fix my own script, so I hope it is also helpful to the rest of you. 😉

_Josh

[dr3do]

Have found this one: [code]/usr/share/servermgrd/bundles/servermgr_sharing.bundle/Contents/copyprivs[/code]

[kimerajamm]

[QUOTE][u]Quote by: dr3do[/u][p]Have found this one: [code]/usr/share/servermgrd/bundles/servermgr_sharing.bundle/Contents/copyprivs[/code][/p][/QUOTE]
thank for that 🙂 🙂

[Author]

Posts