This shouldn't happen, and doesn't on my system.
#Batchmod permissions mac os x
I'm not sure what else would cause that button to be disabled.ĭual 2.7GHz PowerPC G5 w/ 2.5 GB RAM 17" MacBook Pro w/ 2 GB RAM - Mac OS X (10.4.8) I have no idea if this is at all related to the issue you're having, but it sounds like it could be. to adjust the BSD-based permissions didn't work, since the volumes had ACLs enabled which were overriding the BSD permissions structure.Īfter rebooting into Server, I was able to use one of the included programs to turn off ACLs for all volumes and then the behavior in the client version of Tiger returned to normal. Trying to use a utility like the Finder's permissions section, Batchmod, XRay, etc. I also recall that some volumes showed an odd ownership and I wasn't able to modify the root level of them. Have any of these volumes ever come into contact with OS X 10.4.x Server? By default, I believe Tiger Server enables Access Control Lists (ACLs) for all volumes on the system, which can often cause odd behavior when you're booted from a normal client version of Tiger.įor example, after installing Server on one of my partitions and starting up from it and playing around, after I rebooted to my normal Tiger partition the "Ignore ownership on this volume" checkbox had disappeared from the Ownership & Permissions section of the Finder's Get Info window for all volumes on my Mac (not just the boot volume, which normally doesn't have that checkbox).
0 kommentar(er)
