Hi Matt, There is nothing for you to worry about here. They are not actually errors; it’s just the Permissions database hasn’t been updated for the OS yet. And you can disregard any that begin with l, as in should be lrwxr-xr-x , they are lrw-r—r—
The l before the Permissions is a Unix symlink, somewhat like an alias; it just means some components have been moved to a different location, but the old database is still being used. They are not errors. They can not be "repaired." There is nothing to repair. There is nothing you can do to “fix” the “problems” because there is no problem to fix. As far as the permissions database knows, that is supposed to be the actual file, not a link to the file (the l in lrwxr-xr-x). If Apple updates something but doesn’t update the repair permissions database to reflect the change, it will post the note you see (or something similar). Even though it says “repaired,” it isn’t because it can’t be. There is nothing wrong; it’s just different. They are not truly errors. Note that they begin with “User differs” or “Permissions differ.” Those are simply alert messages. Same with those containing SUID. Ignore them. They won’t go away and will appear every time you repair permissions. They cause no harm. Have a glass of red, put your feet up and relax, you are ok ;-) Cheers, Ronni 17" MacBook Pro 2.3GHz Quad-Core i7 “Thunderbolt" 2.3GHz / 8GB / 750GB @ 7200rpm HD OS X 10.6.8 Snow Leopard Windows 7 Ultimate (under sufferance) On 03/07/2011, at 8:25 PM, Matt Falvey wrote: > > Hi I have just ran the 10.6.8 update and strictly followed Ronni's Combo > Update list. > > I have just got to Step No. 7. Repair permissions and ran it and had loads > and loads of events on it. They seemed to be mainly related to two of the > three Software updates that I ran in Step No 6 Run Software Update, those > are: Airport Utility and Java. > > Anyway the final note was Warning: SUID file > "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ArdAgent" > has been modified and will not be repaired. > > Followed by Permissions Repair Complete. > > This was run on the actual disc WDC WD101EADS-65L5B1 Media. > > As it seemed as if the SUID file, whatever it is, had not been repaired, I > ran Repair Disk Permissions again expecting it to deal with just it and let > me know if it could fix it or not. Instead it went through another 8 or so > minutes of similar repairs to the files, I would say identical, but I did not > record them but the system seemed to concentrate on Airport Utility and Java > and changing -rw-rw-r-- to -rw-r--r-- or lrwxr-xr-x to -rw-r--r-- and ended > up again with the same warning. Now I know nothing of what the Permission > repairs is trying to achieve, but if it has already done it once, why did it > have to do it again? > > Well, as I was still get the Warning message, I thought I might try and > repair the permissions on the HD instead. So I ran Repair on the HD, well it > told me it was going to take 8 minutes, but took a lot less time, still gave > me loads of Airport Utility and Java errors of the type mentioned above and > finished again with the same SUID warning. > > What do I do? Do I keep repairing permissions 'till I get no errors? Or do > I presume that the statement "Permissions Repair Complete" is a fact, even > though I know it is not, as each subsequent running of it has shown me? > > What does the SUID file warning mean? It has been modified, does that mean it > is broken? Will not be repaired, does that mean it is not necessary to > repair? Does anyone have any idea what it does and how it would have become > modified? > > Thanks. > > Matt Falvey. > -- The WA Macintosh User Group Mailing List -- Archives - <http://www.wamug.org.au/mailinglist/archives.shtml> Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml> Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>
