Repair Disk Permissions question...

I keep getting this after I repair disk permissions :
"Permissions differ on "System/Library/LaunchDaemons/com.apple.usbmuxd.plist", should be -rw-r--r-- , they are -rwxr-xr-x .
Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" has been modified and will not be repaired.
Group differs on "private/etc/cups", should be 0, group is 26.
Permissions differ on "private/var/spool/cups/cache/rss", should be drwxr-xr-x , they are drwxrwxr-x ."
Can someone please tell me what this means?...and especially the Warning: SUID...something modified and will not be repaired?...is this something I should be concerned about?...
Wasn't sure where to put this question...if it's in the wrong place please tell me and i'll post it elsewhere...
Thanks for help in advance...
M
Message was edited by: Morris Taub
Message was edited by: Morris Taub

Hi Morris,
Here's the Apple article on the subject:
http://support.apple.com/kb/TS1448
Apparently it is not a problem. Mine started giving these after the 10.5.5 update.

Similar Messages

Repair Disk Permissions utility stalled - I have read the knowledge base

I have researched the knowledge base and search for posts on this and cannot find answer: Running 10.4 at the latest version. used the original install 1 disc I received with Tiger to repair disc permissions (like Apple support has told me to do in the past, but my current research said I do not need to do this unless certain parameters are met, and none of the parameters applied, but oh well, I am here anyway). Cold Boot from the original install disc 1 and slected the start up disk I use (I only have one start up disc/drive). Did a repair disc permissions and got a long running routine that reporting a lot of fixes, then the utility has stalled -- no progress on the progress bar. I "stopped" the process using the "stop repair" button (three times). The log reflected the utility stopped, but the progress bar still is blue and not moving (for a couple of hours). When I go to quity File >Disk Utility, it warns me that Disk Utility is running and this may make my system unstable/unsuable.
QUESTION: CAN I JUST QUIT DISK UTILITY AND NOT HAVE ANY ADVERSE AFFECT ON MY IMAC DRIVE?

Thanks for your advice, I still have an issue:
-after the first repair disk permission "stalled" process, I exited Disk Utility and cold booted the machine after I had disconnected all external devices other than the original iMac keyboard
-obtained the combo patch for 10.4.7 from the Apple download site (it had already been installed but I reinstalled per your advice)
-re-applied the combo patch and then did another cold boot
-ran Disk Utility from the original Tiger install #1 disk, and then selected "repair disk permissions" for my start up disk (I only have one)
- process ran for 10 minutes or so then gave the following error message: "Disk Utility Error: Disk Utility has lost its connection with disk utility management tool and cannot continue. Please quit disk utility and re-launch disk utility"
- I pushed the "stop disk permission repair" button, then quit disk utility, then cold booted the machine again.
-re-applied combo patch as above, then cold booted the machine
-ran disk utility from the original iMac install #1 disk, ran "repair disk permissions", and then received the same error message as above.
- I then just quit Disk Utility and cold booted the machine again and went about my business. There does not seem to be any problem with the machine (was not before, but I ran repair permissions thinkging this was a routine maintenance taks that should be run)
- in my prior search of the knowledge base, I found the following information about repair disk permissions:
Location: http://discussions.apple.com/thread.jspa?messageID=607495&#607495
How often should I Repair Permissions?
You do not need to Repair Permissions on a regular basis.
There are only three occasions you need to do this:
1. When you have just installed something that required you to run an Installer, rather than just copying some software to a folder. This should be done for both Apple and non-Apple software.
2. When you have been working on your OS X files or folders while booted from OS 9, or remotely connected via a non-OS X machine, since OS 9 and other systems do not handle OS X's permissions correctly.
3. The other case is if your system is behaving strangely, when you should run Disk Repair from your CD followed by Repair Permissions. This is just to eliminate these things before going on to further trouble-shooting.
Otherwise you can happily forget about Permissions!"
So, it would appear I do not need to do anything else; the machine seems to be working properly. Is there anything else I need to do? thanks for the help! Bob

Need advice on Repairing Disk Permissions...

I need some input from those who know how to Repair Disk Permissions (under Disk Utility, for those who don't know).
Basically, I lost a TON of my Access and Privileges on my G4 recently--which I really only noticed after iTunes would no longer let me import anything (no matter how many times I tried changing the Ownership & Permissions on my Music folder's Info section)--which, I might add, I suffered due to a virus caused by Limewire. As had been suggested to me, I Verified Disk Permissions, and saw that I had a TON of problems listed on my startup HD. So I'm now seeking ways to repair them.
Now, the most obvious way is using the Repair Disk Permissions program (which I've actually never had to use before). However, under OS10.3.9, when I select the Repair Disk Permissions on Disk Utility, in listing all my Drives available, it actually shows the drive in 2 formats/pictures:
1) the actual technical name/manufactor model/GB size of the drive (on top), and
2) the Desktop name and Icon picture of the Drive as it appears on my desktop.
This confuses me: as you can guess, the startup Drive in question is only partioned as one. So on Disk Utility, which of these 2 pictured drives do I have to highlight and Repair Disk Permissions to (i.e. 19GB Maxtor32049 Vs. 'HAL')?
Also, for those of you who have used other means (programs) to change Disk Permissions, which would you recommend? For example, I got a program from Versiontracker called BatCHmod, but I don't know if something like it is any safer than just using Repair Disk Permissions. Because unfortunately, I'm running out of room on my disk, and don't have nearly enough space on my other drive to hope to back the whole Drive up to.
Please help!!!

Hi phasmatrope!
TO REPAIR PERMISSIONS ON THE STARTUP DISK
1.Open Disk Utility, located in Applications/Utilities, and select the startup disk HAL, in the left column.
2.Click First Aid.
3.Click Verify Disk Permissions to test permissions or Repair Disk Permissions to test and repair permissions. (I never "Verify". Just run "Repair".)
Rerun RP until the only message it reports is:
"We are using special permissions for the file or directory ./System/Library/Filesystems/cd9660.fs/cd9660.util.
New permissions are 33261"
This is a status message and not a cause for concern. You may safely ignore it.
Or these:
"We are using a special uid for the file or directory ./private/var/at/jobs. New uid is 1"
"We are using a special uid for the file or directory ./private/var/at/spool. New uid is 1"
Again, these are status messages, which appeared after Security Update 2005-001.
There may be others that you can ignore. Complete lists at link below.
Spurious Permissions Errors In 10.3.x
When "Repair Permissions" is complete. Quit "Disk Utility".
Good Luck!
ali b

Repair Disk Permissions: is it a safe operation ?

Hello,
I'm preparing for the 101 course and, reading about the Verify/Repair disk permissions utility, I wanted to test it on my mac.
I launched the verification on it and I see "lot" of unexpected entries (see below):
Verifying permissions for “Macintosh HD”
Permissions differ on “System/Library/User Template/ar.lproj”; should be drwxr-xr-x ; they are drwx------ .
User differs on “usr/share/collabd/coreclient/public/locales/zh_CN.lproj”; should be 94; user is 0.
Group differs on “usr/share/collabd/coreclient/public/locales/zh_CN.lproj”; should be 94; group is 0.
User differs on “usr/share/collabd/webauthd”; should be 94; user is 221.
Group differs on “usr/share/collabd/webauthd”; should be 94; group is 221.
User differs on “usr/share/collabd/webauthd/locales”; should be 94; user is 221.
Group differs on “usr/share/collabd/webauthd/locales”; should be 94; group is 221.
User differs on “usr/share/collabd/webauthd/locales/zh_CN.lproj”; should be 221; user is 0.
Group differs on “usr/share/collabd/webauthd/locales/zh_CN.lproj”; should be 221; group is 0.
Group differs on “Library/Java”; should be 0; group is 80.
Permissions differ on “Library/Java”; should be drwxr-xr-x ; they are drwxrwxr-x .
Permissions differ on “System/Library/User Template/cs.lproj/Pictures/iChat Icons”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “System/Library/User Template/hu.lproj/Pictures/iChat Icons”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “System/Library/User Template/tr.lproj/Pictures/iChat Icons”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
User differs on “usr/share/collabd/coreclient/locales/zh_CN.lproj”; should be 94; user is 0.
Group differs on “usr/share/collabd/coreclient/locales/zh_CN.lproj”; should be 94; group is 0.
Permissions differ on “usr/share/devicemgr/frontend/admin/zh_TW.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/zh_CN.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/ru.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/ko.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/nl.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/it.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/es.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/fr.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/de.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/ja.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Group differs on “Library/Documentation/Applications/iTunes/Acknowledgements.rtf”; should be 0; group is 80.
Permissions differ on “Library/Documentation/Applications/iTunes/Acknowledgements.rtf”; should be -rw-r--r-- ; they are -rw-rw-r-- .
Group differs on “Library/Documentation/iPod/Acknowledgements.rtf”; should be 0; group is 80.
Permissions differ on “Library/Documentation/iPod/Acknowledgements.rtf”; should be -rw-r--r-- ; they are -rw-rw-r-- .
Group differs on “.DS_Store”; should be 80; group is 0.
Permissions differ on “.DS_Store”; should be -rw-rw-r-- ; they are -rw-r--r-- .
User differs on “Applications/.DS_Store”; should be 0; user is 501.
Permissions differ on “Applications/.DS_Store”; should be -rw-rw-r-- ; they are -rw-r--r-- .
Group differs on “Library/Preferences/com.apple.alf.plist”; should be 80; group is 0.
ACL found but not expected on “private/var/root”
ACL found but not expected on “private/var/root/Library”
ACL found but not expected on “private/var/root/Library/Preferences”
Permissions verification complete
It seems to me that these are all related to system files, things that weren't changed by third-party applications or by me.
The question are:
- why an untouched system would have errors in the permissions ?
- is it safe, since I haven't got until now problems with permissions on that os, to repair these errors or it's better to leave everything as it is now ?
Ciao,
Nicola

Hello Nicola,
You raise a touchy area for discussion...some users on here are very opposed to repairing permissions, others are strongly in favor of repairing permissions before and after software installation.
The permission statements you see do not generally adversely affect the system but they are not the permissions disk utility has been told to expect. Those may be artifacts from the installation process and why we have been told in the past to always repair permissions after installing/updating the operating system.
Since you ran verification, if you run repair you will end up cleaning up a lot of this "discrepancies" with what disk utility wants to see.
Repair permissions is safe, and I tend to use it every time I upgrade or install software.
Ralph

Repairing disk permissions keeps giving same message

I routinely verify my HD and repair disk permissions. The latter often indicates repairs are needed, especially after installation of new software or updates (I repair before and after). But once repaired, if I verify the permissions they come out ok -- i.e., no repairs are needed. Until just recently. I am now getting the following message after repairing permissions:
Verify permissions for “Macintosh HD”
Determining correct file permissions.
Permissions differ on ./private/var/log/secure.log, should be -rw------- , they are -rw-r-----
Permissions verification complete
The privileges have been verified or repaired on the selected volume
If I verify permissions after repairing this, I get the same message again. So the repair is not holding. I am running OS X 10.4.11 and I recall that on earlier OS's there were sometimes innocuous repairs that kept being required, but that were not really a problem. But under 10.4.11 a repair has usually been good, and clears the deck. Until now. Any ideas?
Update: I am no longer having this problem. Possibly I was clicking on the verify permissions button instead of the repair button. I have used DU many times, so this would be a fairly boneheaded thing to do at this point. Maybe familiarity breeds carelessness? In any event, I often get the message above when I check disk permissions, and I would be curious to know why it is one of the more common repairs needed. So let's make that my question instead...
TIA
Message was edited by: Drake Bradley

Not to worry about it, that secure.log is a common one for that.
Repair Permissions checks Library>Receipts to find out the proper Permissions, that file's Permissions may exist in more than one and/or some OS component doesn't know the new/latest permissions when using it.

Why isn't Disk Utility clear after "Repair Disk Permissions"?

Having used my computer for several days I decided to use Disk Utility to “Repair Disk Permissions” after a few hours of use.
2008-11-29 08:30:17 -0800: Disk Utility started.
2008-11-29 08:30:24 -0800: Repairing permissions for “Macintosh HD”
2008-11-29 08:30:24 -0800: Reading permissions database.
2008-11-29 08:30:24 -0800: Reading the permissions database can take several minutes.
2008-11-29 08:43:29 -0800: Permissions differ on "private/var/log/secure.log", should be -rw------- , they are -rw-r----- .
2008-11-29 08:48:26 -0800: Group differs on "private/etc/cups", should be 0, group is 26.
2008-11-29 08:48:28 -0800:
2008-11-29 08:48:28 -0800: Permissions repair complete
2008-11-29 08:48:28 -0800:
2008-11-29 08:48:28 -0800:
I shut down the computer, turned off its power for 1 minute and restarted. I initiated Disk Utility once again.
2008-11-29 09:16:42 -0800: Disk Utility started.
2008-11-29 09:20:55 -0800: Repairing permissions for “Macintosh HD”
2008-11-29 09:20:55 -0800: Reading permissions database.
2008-11-29 09:20:55 -0800: Reading the permissions database can take several minutes.
2008-11-29 09:38:47 -0800: Group differs on "private/etc/cups", should be 0, group is 26.
2008-11-29 09:38:49 -0800:
2008-11-29 09:38:49 -0800: Permissions repair complete
2008-11-29 09:38:49 -0800:
2008-11-29 09:38:49 -0800:
When Disk Utility was finished, I clicked on “Clear History” and reran “Repair Disk Permissions.”
2008-11-29 09:42:01 -0800: Repairing permissions for “Macintosh HD”
2008-11-29 09:42:01 -0800: Reading permissions database.
2008-11-29 09:42:01 -0800: Reading the permissions database can take several minutes.
2008-11-29 10:00:19 -0800:
2008-11-29 10:00:19 -0800: Permissions repair complete
2008-11-29 10:00:19 -0800:
2008-11-29 10:00:19 -0800:
Now everything seems clear.
My question...
Why did I initially see:
2008-11-29 08:43:29 -0800: Permissions differ on "private/var/log/secure.log", should be -rw------- , they are -rw-r----- .
2008-11-29 08:48:26 -0800: Group differs on "private/etc/cups", should be 0, group is 26.
and why after restarting should I end up with only
2008-11-29 09:38:47 -0800: Group differs on "private/etc/cups", should be 0, group is 26.
and after “Clear History” and rerunning Disk Utility why is everything clear until I start using the computer again?
I’ve had it explained that “Group differs on "private/etc/cups", should be 0, group is 26” is not meaningful, but I’d like to know WHY it happens. I’d also like to know why “ Permissions differ on "private/var/log/secure.log", should be -rw------- , they are -rw-r----- .” initially appears.
Thank you,
ZTIWYM3ZUI

As a casual "Apple Discussions" user it hadn't occurred to me that if a question had been answered previously, it should never be asked again.
It's not that. It's because the problem's been beaten to death over the past fourteen months, since Apple shipped Leopard, that most consider it common knowledge, no matter where one's been visiting or how often. Every Apple/Macintosh related website has addressed the never ending issue. Finally, since the forums Help file says:
*I have a question or issue—how do I search for answers?*
+It's possible that your question or issue has already been answered by other members so do a search before posting a question. On most Apple Discussions pages, you'll find a Search Discussions box in the upper right corner. Enter a search term (or terms) in the field and press Return. Your results will appear as a list of links to posts below the Search Discussions Content pane.+
+You can also refine your search by using the options in the Search Discussions Content pane. Click the Search Tips link for help with our search features. You can streamline your results by restricting your search terms by category or forum, specifying a date range, or searching for posts by username. You can also search the User Tips Library.+
Maybe that should be retitled: *+I have a question or issue—how do I resolve it?+*
Just out of curiosity, I wonder if any of these exceptional people can figure out my signature.
ZTIWYM3ZUI - "time is what you make—use it" or something of that nature.

Older iMac slows then repairing disk permissions fixes - culprit?

Mom's older iMac 350 running Panther is fine and then every so often it slows down significantly (even closing windows is very slow).
Running Disk Utilities repair disk permissions always seems to solve the problem.
Just curious if anyone knows what's going on here. This doesn't occur frequently, I think we've only done this twice in the past 8 months. Just curious what the culprit is here & has anyone else experienced this.

Hi mjp29,
even the best quality machines need some regular maintenance (MacOS X 10.3/10.4: System maintenance). Just think of your car and what would happen if you never changed/added some oil...
If this answered your question please consider granting some stars: Why reward points?

Repair disk permissions shows problem

trying to get a printer installed I ran repair disk permissions and came up with a problem.
Question, how do I resolve it?
message is: System/Library/CoreS cannot be repaired.
I need advise from someone a lot smarter than me.
I have not noted any problems with any component or aspect of the os other than this one Epson printer which will not install.
Not sure if re-install of SL would correct problem or cause changes to current setup.

no, this is not the full message. it's still truncated. there is no such thing as "System/Library/CoreS". there is a directory "System/Library/CoreServices" which contains a lot of stuff. the message likely refers to something in that directory. but as I said, all such SUID messages are harmless and should be ignored.

Repair Disk Permissions taking 19 hours so far...

I semi-regularly use Onyx to repair disk permissions. (probably once a month). It normally takes around 30 minutes to complete. Yesterday my system started hanging so I ran repair disk from the boot cd. This was fine and took around fifteen minutes. Then I ran repair disk permissions from the boot CD. After around 30 minutes it said '1 minute remaining'. That was 19 hours ago....
It's still chugging along so it sounds like somethings happening - but the progress bar and remaining time have not changed.
So my question is - should I let it finish? How long should I wait? Is there anything else I could check?

Update to the Update!
I ran repair disk permissions from my profile and it finished (around 7 minutes). I've attached the log below in case it points to anything specific?
2010-09-05 10:08:37 -0500: Repairing permissions for “Macintosh HD”
2010-09-05 10:13:39 -0500: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/deploy.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
2010-09-05 10:13:40 -0500: Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/deploy.jar".
2010-09-05 10:13:40 -0500: Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/libdeploy.jnilib", should be -rwxr-xr-x , they are lrwxr-xr-x .
2010-09-05 10:13:40 -0500: Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/libdeploy.jnilib".
2010-09-05 10:16:31 -0500: Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
2010-09-05 10:21:27 -0500:
2010-09-05 10:21:29 -0500: Permissions repair complete
2010-09-05 10:21:29 -0500:
2010-09-05 10:21:29 -0500:

"Repair Disk Permissions" keeps showing the same permission differences

After the recent software updates, I suddenly cannot use my eFax Messenger. This happened once before, but I was able to fix the problem by running "Repair Disk Permissions" in Disk Utility.
This time "Repair Disk Permissions" did not fix the problem. Not only that, I noticed the same permission differences showing up again and again when I repeated Repair Disk Permissions.
Is the permissions database no longer accurate? Does anyone have any suggestions on how to resolve the permission differences? I notice that others have reported similar issues on this forum, but no definite resolutions have been posted.
Thanks for any help you can give me.

..."As long as the repair ends up with the message 'repairs complete' or words to that effect, you are OK."...
I don't know who started with the "repairs complete means everything is fine" business, but they were wrong and it is repeated far too often by too many people on this site.
Considering all of the messages erroneously being dismissed as "informational", it is ironic that the one message that is actually just "informational" is the one being given special significance.
The "repairs complete" message only means that the process has stopped. Try starting to repair permissions, then immediately click the "Stop permissions repair" button. Try logging in to a non-admin account and start a run -- when a password is requested, cancel. Try repairing permissions when there are problems with the permissions database. You will see messages such as "Stopped by user", "insufficient privileges" or "underlying task reported failure on exit, but in every case, the report will end with the "Permissions repair complete" message.
With respect to the OP's question, the overall "repair permissions" system as it stands in 10.5 has the appearance of an unfinished product (it received major revisions in the transition from 10.4). Without specific details, all anyone can say is that the error messages are likely false positives - except for any true positives that might be present among them.

Repair disk permissions "greyed out"

We have a G5 with 2 internal hard drives that we use as a server. I can run "repair disk permissions" on one drive, but on the other the choices for repair or verify disk permissions is greyed out. Why is this and how can I repair the permissions on the one drive?

2 possibilities come to mind.
(1) The disk in question does not have Mac OS X installed on it (required for permission repair).
(2) The disk in question does not have suitable files in the /Library/Receipts folder (such a folder doesn't exist, I guess, if OS X isn't there - see (1)).
charlie

20 minutes to Repair Disk Permissions. Every time.

In trying to diagnose some other issues, I have had to repair disk permissions several times over the past week. Each time I have run it, it was 15 minutes before it was finished and each time (if I remember correctly) I have been met with a slew of messages like this one:
Group differs on "Applications/Utilities/Disk Utility.app/Contents/Frameworks/DUSupport.framework/Versions/Current", should be 80, group is 0.
I cannot remember if the "should be" was always 80, but the "group is" was always 0. Does anyone have some insight on this one? Is this bad? I can't say that I get any sense from the message that permissions were repaired. I do not know if the files in question have been the same each time or not.

repair permissions takes much longer in leopard. 20 minutes is quite normal on your hardware. I think that group difference message is harmless and can be ignored but you can change the group on Disk utility and other apps if you want to.
The group on everything in the Applications folder should be admin (gid=80).
Run the following command in terminal
*sudo chgrp -R admin /Applications*
you'll have to enter you admin password (which you won't see) that's normal.

Verify disk permissions question....

Verify permissions for “Macintosh HD”
ACL found but not expected on "Applications/Utilities".
ACL found but not expected on "Applications".
ACL found but not expected on "Library".
I verified my permissions on my internal disk with all my externals disconnected... this is what I got as a report. what does this mean and what should I do?
fresh install of Leopard and FCS2
also I still have Tiger and FCS1 (carbon copy cloned) on an external drive and it was hooked up to my iMac while I did the clean install of Leopard. now whenever I run FCP it will sometimes spin up the external and search for something even though I do not have it set for a scratch drive or anything.... what is going on? should all externals be disconnected while doing a fresh format and install of OS and Apps?
thanks for all your help.
DROCK

ok I found this article so I guess that answers my first question.... what about the disk spin ups????
thanks
issue or symptom
The following messages may appear in the Disk Utility log window when repairing disk permissions.
Warning: SUID file "usr/libexec/load_hdi" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Reso urces/Locum" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner " has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconf ig" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/writecon fig" has been modified and will not be repaired.
Warning: SUID file "usr/libexec/authopen" has been modified and will not be repaired.
Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" has been modified and will not be repaired.
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
"Any message that starts with: 'ACL found but not expected on...'."
Products affected
Mac OS X 10.5 Leopard
Solution
You can safely ignore these messages. They are accurate but not a cause for concern.

Leopard buggy and repairing disk permissions odd. realated?

Since installing 10.5 I've been having problems with apps quitting unexpectedly -- mostly mail, safari, and Final Cut suite programs.
When I repair permissions, I get this (which is new since installing leopard also):
Warning: SUID file "usr/libexec/load_hdi" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Reso urces/Locum" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner " has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconf ig" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/writecon fig" has been modified and will not be repaired.
Warning: SUID file "usr/libexec/authopen" has been modified and will not be repaired.
Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" has been modified and will not be repaired.
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
Permissions repair complete
Is there any connection? Should I fix the situation that doesn't allow Dick Utility to repair my permissions? The apps quitting are driving me crazy!
Thanks!

There's no connection. See:
Mac OS X 10.5: Disk Utility's Repair Disk Permissions reports issues with SUID files
Also, it's always a great idea to search the forum for keywords related to your question before starting a new thread -- there's often someone else out there asking the same thing, and sometimes even an answer. This question, for example, has been asked dozens of times.

Installing a trial version of the Illustrator and InDesign App in Creative Cloud on my Mac is impossible. Keep getting 'Installation failed' notices. More information gives 0 fatal error(s), 0 error(s). Already repaired disk permissions in Disk Utility bu

Installing a trial version of the Illustrator and InDesign App in Creative Cloud on my Mac is impossible. Keep getting 'Installation failed' notices. More information gives 0 fatal error(s), 0 error(s). Already repaired disk permissions in Disk Utility but nothing seems to work. Exit code: 7.

Hi Maarton,
Please follow the link to resolve the issue: Errors "Exit Code: 6," "Exit Code: 7" | CS5, CS5.5
-Ankit

Repair Disk Permissions question...

Similar Messages

Maybe you are looking for