Warning: SUID file has been modified and will not be repaired.

Very Strange. I am having the same issues. Same alarming message from disk utility. Same long wait when disk utility runs. Also, I just ran "verify permissions" on another computer, a G4 ibook running 10.5 and it found nothing. Though it did take it's time running. All the best.

I wiped my drive, repartitioned and did a clean install of 10.5. I have the same issues with my SUID, permission repair times are very long, problem is not fixed when using disk utility from the install disc, and to add [not sure if this is linked] my Time Machine back Ups have failed 3 times starting with the initial attempt all resulting in a kernel panic and forced shutdown dialogue box.

A fix is needed!

Yeah I also do think the same, it reminds me of the "system.log" message a lot of OS X users used to see when they repair permissions on OS 10.4.8 and above.

Add me to the list. I noticed it right away after I installed Leopard. I'd ran Repair Disk Permissions soon after a clean install.

Has anyone got this fixed? And is there anyone using Leopard that doesn't have this problem?

The Remote Desktop Client update is why this is happening. Didn't you notice this didn't appear in a fresh install without the update? So a permissions check error introduced by an Apple software update -- I wouldn't lose sleep over this.

Ok,

I too have the message. I take it Apple will fix this soon? In the meantime, does anyone have any ideas? I am not experienced using terminal, but would appreciate any other ideas. Running the disk utility from the Leopard Disc, did not fix the problem with me. It seems that this occurred after we all did the Software update after installing leopard. The culprit: Remote desktop Client.

Matt

Add me to the list. Doesn't seem to make any difference if I run Disk Utility from the internal drive or the install disk.

So why hasn't apple even responded to this thread? They've been acting like Microsoft more and more and it kind of stinks.

Here's the reason:

Repairing permissions (which isn't a necessary task and you've all wasted part of your lives worrying about it, time which you'll never get back) just compares the permissions on files installed by Apple to the receipt which came with the original package.

ARDAgent is part of the Apple Remote Desktop, which was updated just after Leopard came out. Therefore, the file that Disk Utility is comparing to the receipt is DIFFERENT, and therefore Disk Utility is not going to make any decisions about the permissions. This is NORMAL, and has nothing to do with any perceived problems that people may be having with their computers.

I wish to God that the Repair Permissions button didn't exist.

So why hasn't apple even responded to this thread? They've been acting like Microsoft more and more and it kind of stinks.

Probably because they read the terms and conditions

http://discussions.apple.com/help.jspa

Generally I love people say: "The reason is"...

Question now is: You KNOW it, or you just observed, what Disk-Utility in general does?

Yes, it's a well known fact, that DU does compare rights files have right now to a given standard value.
BUT, IF you are right, why
1. DU needs 10 to 20 times more than it does in Tiger and
2. It eats up a LOT of CPU during the "repair".

So, as far as I can tell we are NOT finished here and might even wait on 10.5 :-/

That has nothing to do with what Paul said. He's just saying why people make a big fuss about a different permission setting that came about as a result of an updated file and is likely not to affect overall OS behavior.

Well, I believe that Leopard checks the file checksum and compares it to the one stored in the "Bill of Materials" (.bom file) in the associated receipt package (/Library/Receipts). It's the computation of the file checksums that requires time and taxes the CPU. Tiger didn't do this -- it simply assumed the file was the same and compared the permissions with those in the BOM.

However, I think Leopard checks the checksums for ALL files listed in the receipts, and that isn't absolutely necessary. It should be checked for anything with SUID permissions, and any kernel extensions, but anything else ought to be OK.

Incidentally, you can use Terminal.app and do

*lsbom -pfcM /Library/Receipts/Essentials.pkg/Contents/Archive.bom | grep MacOS/ARDAgent*

then

*cksum /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent*
*ls -l /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent*

and manually check that the checksums and permissions are the same. The error message you see is telling you that the checksums are not the same, so it's going to skip changing the permissions on ARDAgent.

What it's saying is "This file has been modified (it has a different checksum than I'm expecting), and as it's something that runs with elevated user rights I'm erring on the side of caution and not touching it as it may be compromised" -- the actual error message is a little terse and poorly worded, perhaps, but that's UN*X for you. 🙂