From “removeUnexpectedACL” to “ACLr8″

July 8th, 2009

I just received a huge shipment of cheese and I don’t know what to do with it. So, I’ll be changing the name of the ACL tool from “removeUnexpectedACL” to “ACLr8″. But who cares?

Download ACLr8 here.
Update: ACLr8 now has its own page here.

Tags: , , , , , , , , , , , , , , ,

  • I don't know why it wouldn't work for you, I've only heard success stories so far.

    Send me a list of the files that are reported to have unexpected ACL, I'll see if I can figure it out. Just run a permissions check in Disk Utility, paste the results into an email and send it to me.
  • rei
    Hi,

    I ran your script, but there seems to always be the same 54 files with unexpected ACL that doesn't seem to get fixed with the sudo chmod -N command. Any ideas?
  • Actually, the man entry for chmod is very clear about -N. Here's a quote from the output of "man chmod":

    -N Removes the ACL from the named file(s).

    Although Apple is right to say you can safely ignore these messages, some prefer not to, as they cause the run time of a permissions repair to increase drastically.
  • Joe F.
    Thanks for the quick follow up.
    I understand that -N is a parameter, but the man isn't clear on what it is. Evidently there are LOTS of optional parameters and switches.

    Also, for for the benefit of anyone else exploring the unfixable permissions dilemma, it appears that Apple has finally deigned it appropriate to issue a tech note June 26, 2009:
    http://support.apple.com/kb/TS1448?viewlocale=e...

    Cheers...
  • Joe F.
    I found this page/script as probably many others will: searching for ACL/permissions mentions in Google.

    I looked at the script (as advised) and, knowing (practically) nothing about command line crap, checked the 'naughty bits' :
    for file in filesWithUnexpectedACL:
    os.system('sudo chmod -N ' + file)

    If you: "man chmod -N" you get a 'no such thing' sort of reply.

    Error or inspired genius?
  • Joe,

    Thank you for your concern. You did right to check the script before executing it.

    However, you have erroneously perceived a problem. You see, the unix executable I use is not "chmod -N" but rather just "chmod", using "-N" as a parameter. If you type "man chmod" into Terminal, you should get the information you were looking for. I do hope this script has been helpful to you.

    Best,
    Fletcher Tomalty