ACL found by repair permissions

Question

OK, here is what we have. Macbook 1 died. Macbook 1 was on Time Machine. Did a restore from Time Machine to MacBook 2. Every since then, when I repair permissions the following comes up:
Repairing permissions for “Macintosh HD”
ACL found but not expected on "private/etc/apache2/users".
Repaired "private/etc/apache2/users".
ACL found but not expected on "Library/Preferences/Audio".
Repaired "Library/Preferences/Audio".
ACL found but not expected on "System/Library/Keychains/X509Anchors".
Repaired "System/Library/Keychains/X509Anchors".
ACL found but not expected on "private/var/db/launchd.db/com.apple.launchd".
Repaired "private/var/db/launchd.db/com.apple.launchd".
ACL found but not expected on "private/var/yp/binding".
Repaired "private/var/yp/binding".
Permissions repair complete
My question is: How do I remove the ACL?
Repair permissions, Disk Warrior, TechTools Pro do not repair.
I would imagine that some place in the "man" pages this information could be found, but I sure cannot find it.
Thanks.
Steve H

Answer 1

First of all, I should point out that I think I understand that these messages are OK to ignore.
Second, I ran your/Kappy's Terminal command suggestion and now the message I should ignore and gone. (yippie) Many thanks to the Florida contingent.
My point is, why should you keep getting the same message, over and over if you should ignore them? If we should ignore them, stop showing them to us. It drives some of us crazy. And for some of us, it's a very short drive.
If you shouldn't really ignore the messages, then either actually do something to address them, or tell us what to do. Which hopefully for most it's not running Terminal commands.
The other thing is, Disk Utility does say it repaired something.
Repaired "private/etc/apache2/users".
Did it really repair something?
If so, why does it constantly repair the same reported issue, over and over?
It appears as if it didn't really repair something.
I'm not trying to be a pain on this issue. lt's just that it seems this is how Disk Utility has worked for some time. I've always wondered why someone at Apple doesn't do something about it.
It's like the old joke, "Doctor it hurts when I do this."
Doctor, "Dont' do that."
Either way, thanks.