"Repair Disk Permissions" leaves sytematcally unfinished work...

... althought it reports they are repared.
This is about the same 16 entries, all in the same folder: System/Library/CoreServices/RemoteManagement/
Today's "Repair" run (extract):
2012-01-15 14:53:43 +0100: Repairing permissions for “Macintosh HD”
2012-01-15 14:55:05 +0100: Permissions differ on “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/pl.lproj/UIAgent.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
2012-01-15 14:55:05 +0100: Repaired “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/pl.lproj/UIAgent.nib”
2012-01-15 14:55:05 +0100: Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/pl.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
2012-01-15 14:55:05 +0100: Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/pl.lproj/MainMenu.nib”
... "Verify" just after (extract):
2012-01-15 15:28:05 +0100: Verifying permissions for “Macintosh HD”
2012-01-15 15:28:59 +0100: Permissions differ on “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/pl.lproj/UIAgent.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
2012-01-15 15:28:59 +0100: Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/pl.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Any idea on how to fix this?
Thank you in advance.

http://support.apple.com/kb/TS1448
As long as it says "Permissions have been repaired" at the end of the report, you're good to go.

Similar Messages

Constantly repairing disk permissions for Spotlight to work

I am constantly having to use Disk Utility and repair my disk permissions in order to get Spotlight to work. Often I'll type something such as an application and the only thing that will show up is the Definition from the dictionary.
Repairing the disk permissions seems to fix the problem, but it doesn't take long before I need to once again go in and repair in order to get Spotlight working again. I've tried dragging the whole hard drive into the exclusions list and then removing it again so the index will rebuild. That also works but again only lasts a short time.
Any help would be much appreciated!

whiskey sour wrote:
I hear a lot about 'defraggin' in Windows. Is there something similar in Mac, ie: is Repairing Disk Permissions something similar?
They're entirely different things. A "defragment" operation moves files around to combine split segments of files and consolidate free space. A "repair permissions" operation examines the permissions settings of system files and resets any that seem to be wrong.
Here's what Apple has to say about defragmenting a Mac disk:
http://support.apple.com/kb/HT1634

I recently repaired disk permissions on my mac HD and now my on-board speakers wont work, the icon is greyed out and only works when my headphones are plugged in.

I recently repaired disk permissions on my mac HD and now my on-board speakers wont work, the icon is greyed out and only works when my headphones are plugged in

Try to put your headphones several times in and out from your connection, might be the switch is stuck. Normally it should work again while trying to plug the headphones in and out!

Working while repairing disk permissions?

Is it ok to do remedial tasks while repairing disk permissions, such as surfing the net, checking email,etc? As long as I'm not installing anything or making system changes?
Thanks,
Wesley

yes, it's quite ok to work while repair permissions runs.

Superdrive replacement not working? Try "repair disk permissions"

Like many other folks, the superdrive in my iMac 7,1 died. I ordered a replacement from Powerbookmedic and installed it following ifixit's guides. Upon booting the iMac I found that the SuperDrive would accept a disc and the iMac saw the SuperDrive but OS X wouldn't recognize any disc I put in the drive and after trying to read it would eject it. After trying various things, I found that other users on my iMac were able to use the new drive just fine, it just wasn't working for me.
I tried various fixes but in the end "repair disk permissions" under disk utility did the trick. Posting here in the hopes of helping others. Joel

I cant access any of the files on the hard drive to back up. Do you know of a link on how to format and reinstall. It would be my first time. I have diskwarrior and it will not load at all.
Under the Erease tab I have
MAC OS Extended
MAC OS Extended (Journaled)
MAC OS Extended Case Sensitive
MAC OS Extended Case Sensitive journaled
MS-DOS Fat

Repair disk permissions does not work

Repair disk permissions does not work. Disk Uitliy fines many incorrect permissions (ACL found, but not expected) and says that it would repair it. However, when checked again, it finds the same permission errors.
I have tried Disk Utility as well as the command line "sudo diskutil repairPermissions /" (which probably does exactly the same as Disk Utility).
Any hints?
C.

Are you trying to Repair Permissions because you have file access problems in the System files, or just because you think you need to do it?
If the former, please explain what you are seeing. If the latter, stop wasting your time.
The things it doesn't repair are not repaired because there is nothing broken. The orginal Receipts files have the old settings, and subsequent updates have changed the permissions on those things to what they should be, now. It will report the differences it finds every time you run Repair Permissions because they will always be different and they should be the way they are.

Repairing Disk Permissions - Not Working with Lion

I simply am not able to repair disk permissions when my Mac is booted normally - the disk utility hangs and never stops - when I boot in recovery more I can run the utility just fine - and then boot as normal. I am wondering what might be causing this or if anyone else is having a similar problem?

With Lion, it is best to do any disk repairs via the recovery partition
And why do you say that? I have heard no such thing, and this was never the case with previous systems. It has always been recommended to repair permissions while booted from the system whose permissions need to be repaired. Do you have documentation that this recommendation has changed?
Joe, repairing permissions works fine for me without needing to boot into recovery mode. Are you giving it plenty of time to finish? Sometimes it may seem to be frozen... sticking on "less than a minute" for well more than a minute, for example. Have you repaired the hard drive (which you do need to boot from the recovery partition to do)?

Repair Disk Permissions not working?

Based on a printer problem, HP suggested that I run Repair Disk Permissions. I did, generating 9 pages of fixes. But if I clear the history and run it again immediately, the same list of repairs is generated, suggesting that nothing was fixed.

It's no problem, see this
https://support.apple.com/kb/TS1448?locale=da_DK

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 Issues

I'm not sure I am posting this in the correct community but here goes . . .
I have a 17" Macbook Pro running the latest version of Snow Leopard. It is almost 2 years old and I have 4 gb RAM.
Recently, it seems to be slowing down and I have to run repair disk permissions 2-3 times a week to recoup a little speed. I also delete my Firefox cache regularly to try to gain a little there. I do make a few videos in iMovie and initially I thought that was the problem but this week I have not really worked in iMovie much and it is still slow. There seems to be some issues in the log of the repair permissions. I hope they show in this image. I don't know what these mean or how to fix them. It is the "permissions differ" entries I am confused about.

You can ignore those permissions per support article
http://support.apple.com/kb/TA21090
Since you brought up iMove, I suspect your storage is nearly full as this most certainly causes the computer to slow down. video files are the biggest culprit.
Look in your Activity Monitor and reduce the drive space by copying to a external, Disk Utility HFS+ formatted external powered drive of unnecessary files so your boot drive is ideally below 50% filled (yea I know but the computer slows down after that) and not more than 75% filled.
Once you have done that. Get another newer external powered HFS drive and download the free Carbon Copy Cloner and clone the internal drive to the external.
Hold option and boot off the external clone, test it out then use Disk Utility to erase the internal and then reverse clone the external onto the internal, this will defragment and optimize your drive so the OS and programs are on the fast part of the drive, not the slow parts.
Reboot into the internal and run off of the free OnyX's maintainence and cleaning aspects and reboot.
http://www.titanium.free.fr/
Sir speedy machine here we come!
Now of course you may have other issues that could be causing your slow down, like not enough RAM or some sort of failed process or leftover program, tweaks or simply a slow Internet.
You can opt to simply reinstall OS X 10.6 ( by holding c and booting off the installer disk ) over your installed version (doesn't touch files or programs) then immediatly Software Updating until clear, that will clean anything hanging out in OS X.
If you still have slowdowns, then it's in what geeks call "User land" basically something installed outside of root, like a program or only runs in user, not in OS X.
For that you need to create a new user, transfer your files via the Shared Drop and wean yourself off the old user and finally delete it. Also install all new versions of your third party programs removing the originals first.
That should do it.

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

Repair disk permissions

why did upgrading my software to snow leopard cause my 'repair disk permissions' to endlessly fail when it never failed once before? by the way i heard all the debate of how repairing disk permissions is or is not important to do. at this point i'm not interested in opinions of why it's important or not i'm just interested in fixing this now existing problem. my software is all updated. any answers appreciated.

     WZZZ wrote:
     "If you updated from Tiger, then you are not used to seeing the same Permissions messages repeated. In      Tiger, repairing Permissions didn't endlessly repeat these."
exactly my point, it worked perfectly. it corrected lines that contained characters that affected my disk burner.
     WZZZ wrote:
     "But these are not errors."
     WZZZ wrote:
     "It means Apple hasn't gotten around to updating the Permissions database (and probably never will.) If you see the same ones, just ignore them."
just ignore the problem=apple failure
thank you for the info

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 Problem

I went to use Onyx yesterday and it asks for my password. I enter my password and it says "Sorry, you entered an invalid password. Please try again. If the problem persists, quit OnyX, repair the permissions with Disk Utility then relaunch OnyX." So I tried. When I am logged in the permissions repair works, but the problem in Onyx persists. So I booted to the install cd and tried there. The process starts but "Reading Permissions Database" never appears in the details and it never moves forward. I'm hoping I don't have to do a reinstall as I used to in my Windows days. Does anyone have a clue how to fix this?
Thanks in advance for the help!

HI,
Launch Disk Utility (Applications/Utilities) and repair disk permissions that way instead of using 3rd party software.
Quit any open applications/programs. Launch Disk Utility. (Applications/Utilities) Select MacintoshHD in the panel on the left, select the FirstAid tab. Click: Repair Disk Permissions. When it's finished from the Menu Bar, Quit Disk Utility and restart your Mac. If you see a long list of "messages" in the permissions window, it's ok. That can be ignored. As long as you see, "Permissions Repair Complete" when it's finished... you're done. Quit Disk Utility and restart your Mac.
Carolyn

Apple: Repair "Repair Disk Permissions"

The Leopard version of Repair Disk Permissions is broke. No matter what it is doing behind the screen, it comes up with the chirpy "Repairing Disk Permissions. Estimated time: Less than 1 minute" then proceeds to wait five minutes (on a 160 GB MacBook Pro of recent vintage) before starting to move the bar from its initial, deceptive, 20% fulfilled position.
This performance and feedback flies in the face of Apple's own software behavioral edicts.
After the five-minute wait, it takes an additional 4:30 to move the bar to the end, even when it's the second run on the same drive. The reported times are NEVER accurate, never even approximate until the last 50 seconds.
And don't even get me started with all the reported failures to fix anything that consistently show up every single time.
In five minutes (300 seconds) my computer has the ability to impose 4.4 Billion computational cycles on the task of sorting out whatever ails my hard disk--per second. That's just a TRILLION point three total mathematical operations that might be brought to bear on thinking about what to do before starting to access the disk and fix its errant map of data.
To give that some scale, at one second per math problem, that equals around 42 thousand years. Which ought to be time enough to evolve the program into a more advanced version...
Message was edited by: Peter Inova1
Message was edited by: Peter Inova1
Message was edited by: Peter Inova1
Message was edited by: Peter Inova1

It's an interesting but irrelevant observation.
Disk Repair is not a mathematical operation - it obviously involves many disk reads - often the slowest component on a computer in terms of access times. Should any repairs be required - the system will then write and likely re-read to ensure the write was successful.
You are trying to figure out future events - how long the next action will take based on prior events - sometimes things change that make past performance a poor estimate of future performance.
As for estimating times - I've programmed this - and observed many attempts to do so - few work well or offer estimates anywhere near accurate. Observe the estimated times to complete a download in iTunes or the time to copy a file. I have seen many cases where the estimates said "10 seconds" and I waited minutes for them to complete.

"Repair Disk Permissions" leaves sytematcally unfinished work...

Similar Messages

Maybe you are looking for