[allenjd]

Found a workaround that seems to be working: sudo chmod -R -N /

This removes any ACLs from all files under the root directory. It stays across reboots and even after installing the recent security update.

[allenjd]

Didn’t seem to help. Thanks anyway. I think I will roll with 10.5.5 with ACLs disabled and see how that goes. Will keep an emergency 10.5.4 image handy though. Maybe 10.5.6 will magically fix things.

[allenjd]

When listing the root directory with ls -l, I noticed the two directories I was having problems with (Applications and Library) were the only to with a + sign after the permissions string. This indicated that the two directories have extended security attributes, ie. an ACL.

One other thing I noticed was that when I did a Get Info on Applications and tried to add my network user, the search in the window would find the user but ot would be added to the list in the Get Info window when I clicked select.

I couldn’t find a command line tool to display or manipulate the ACLs (such as setfacl and getfacl in Solaris) but I found fsaclctl which enables and disables ACL support for a filesystem. I disabled ACL support on / and I could then list the directories using ls as a network users and when I logged in all the icons were correct in the dock.

I’m not sure what effect disabling ACLs on the root volume will have. I guess this is a workaround rather than a solution. I’ll keep looking for a tool to manage ACLs from the command line I guess and try to see what is in there.

[allenjd]

Having the same problem. After the 10.5.5 update network users can no longer read the Applications or Library directories and can not run any applications. The Dock has either question marks or the generic application icon. The permissions in the Get Info window look fine but the folder icons have the do not enter sign on them. More interesting, doing an ls on the root directory from Terminal (copied to another location) reports that Applications and Library do not exist.

I tried detaching and rejoining the OD master and booting from the DVD and doing a permissions verify/repair without much luck.

[Author]

Posts