? Msg from Disk Utility

[testcase]

My MDD (Dual Boot, Dual 1.25GHz, 2GB RAM, OS X 10.5.2) locked up today. I was playing "The Count of Monte Cristo and had paused the game for about an hour. I had to hold the power button to force a shut down. After restarting, I ran Disk Utility and Repair Permission. Repairs take quite a while and, I get:

"ACL found but not expected on "Library"."

I re-ran Repair Permission several times. Always slow and, always the same message.
I did a quick Spotlight check for ACL and, there are hundreds of hits, none of which seem to explain "ACL" Can any Forum gurus shed light on just what's going on here? TIA!

[Joey Cupcakes]

You're on Leopard. That's standard, and means nothing. I wish Apple would fix this so people wouldn't get concerned over not being able to repair a permission that is not broken.

Don't worry about it.

[Panopticon]

If you updated your system to Leopard using the Archive/Install or Upgrade method, your existing users were left with their old membership values, and Leopard doesn't like them.
http://www.macosxhints.com/article.php?s...1291134001

Earlier dicussion of Leopard permissions issues
http://forums.macresource.com/read/1/402...msg-402687

http://docs.info.apple.com/article.html?artnum=307128

[testcase]

Thanks for the info. When I installed Leopard, I used a new 650GB HD and did a new install. I did NOT use Migration Assistant. When I need something from an old HD, I just double click to open it (My MDD has three internal HDs). I hope Apple fixes this soon.

[MacMagus]

The time that it takes for permissions repair is not related to the ACL error. It simply takes ages to verify/repair permissions under Leopard.

That ACL error is generally harmless, but if you'd like to get rid of it there's a simple Terminal command to strip the ACL from the Library folder.

[RAMd®d]

I get the ACL error (several of them actually) on an MB with Leopard installed from the factory.

I've likened this to previous versions of X that gave a long listed of things that we didn't need to know, causing people to think there were problems that have been fixed. The laundry list appeared every time one ran certain versions of DU.

No harm, but it took Apple forever to fix the "problem".

Now, will DU ever get back it's former speed, or is this the way it will be with Leopard.

[MacMagus]

> Now, will DU ever get back it's former speed, or is this the way it will be with Leopard.

What an excellent question!!