- This topic is empty.
-
Posts
-
This is a cut’n paste from an Apple forum submission which is getting no bites. Try your hand at the answer.
OK, here’s one. I am trying to simulate migrating a Panther PDC to a Tiger PDC, and am having some luck here. My current observation is this:
– If I perform an inplace upgrade, all is messy. No explicit ACLs get set anywhere I have seen.
– If I do a migration via the protocol documented at AFP548, I have profile issues. I suspect it’s a rights thing.
– If I do a Tiger install from scratch, and create a PDC and some new users, then do a first time domain logon, the profile folder that gets created has ACLs attached, 4 in particular.
0: (user:owner) Most file permissions
1: (group:daemon) Same
2: (user:owner) 3 Inheritance permissions
3: (group:daemon) SameSo, I’m thinking to myself, I need a script to use chmod to set this up for my hundereds of users that will be getting shipped over to this server. HOWEVER…
There is a user called daemon (System Services) and a group called daemon (Local System). chmod specifically will favor a user over a group when setting ACL’s, and therefore it’s recommended you don’t have a group with the same name as a user. Well, it wasn’t my choice.
So is there any way in a script to set a group ACL of this kind without using WM? I’d hate to have to wear out my mouse hand.
Is there an alternate way to accomplish this?
TIA!
jth
- You must be logged in to reply to this topic.