Repair disk permissions help

Hello all,
im fairly new to the macbook and have been reading up on repairing disk permissions as the mac has started to slow down in time
the problem i have is i opened disk utility
and ran verrify disk permisions, it found problems, so i restarted and held comand and r and booted into the recovery console
from there, i chose disk utilities and ran verify disk again, again it found problems, so i ran repair disk permisons, that came back and repaired succefull,
so just to check i then vefried the permisons again, and once again it found the same problems, so i then re - repaired the permisions, and again it cam back succefull
again i double checked and once again it found the same problems , so im going round in a loop here the problems arnt actually properly fixing?
how can i sort this out?
any help would be appreciated!
regards

Those messages are in fact quite similar to the ones Apple mention in the KB.
All the examples you posted are instances of the same symptom: the BOM states a given path is supposed to be a directory but it actually is a symlink to a directory.
A possible cause of this is when something was installed that did not foresee upgrades that would leave multiple versions installed at the same time, then the development team eventually decided that a new version would be needed to co-exist with the old one and such a new version has been installed. The old BOM file still report the directories (or files) as not being symlinks but the new installation actually moved the old data to a directory specific for the old version, installed a new version and then changed the old directory (aka the "unversioned" or "current" path) to a symlink to the latest installation.
You can safely ignore these differences.
While in the past running permission repair used to be a very important periodic maintenance routine, nowadays it's rarely needed and even more rarely useful. It still is a good idea to run it right before and after an important operating system patch update, but it's not really necessary.
It's very common (and has been for a long time) for the tool to report differences, say they have been repaired, and then, if run again, to report the same differences. In those cases you can generally ignore those differences. Only if the repair tool says it failed to repair something you should be concerned.

Similar Messages

Running the latest OS Mavericks. 8 gigs of RAM. 150 gigs free space on computer. Problem: since upgrading to Maverick almost all applications are slow to open, and frequently many 'spinning ball' interruptions. Repaired disk permissions - no help.

I'm running the latest OS 10.9.1 Mavericks (late 2009 iMac). 8 gigs of RAM. 150 gigs free space on computer. Since upgrading to Mavericks, apps are slow to open, with frequent "spinning ball" interruptions. Repaired Disk Permissions - no help. Repaired disk - no problems indicated. Did notice in going to Utilities/Console that there are 4000 messages over a 3 day period. Any suggesstions how to correct this sudden slow down, other than psychiatric help?

Yes. Many messages show up when I try to use Office for Mac 08. Here's a sample (and one that repeats over and over again):
2/11/14 1:01:16.577 PM Microsoft Word[1912]: OTAtomicAdd32 is deprecated and will be removed soon. Please stop using it.
Also getting many msgs when I use Chrome.

Can't open downloaded game. says need to be administrator. I am. tried 'repair disk permissions/no help...

Unable to open downloaded game. Says need to be administrator/I am. Repair disk permissions w/disk utility no help...what do I do?

This is what popped up after i typed all that in :
Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file
          at java.lang.ClassLoader.defineClass1(Native Method)
          at java.lang.ClassLoader.defineClass(ClassLoader.java:676)
          at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
          at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
          at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
          at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
          at java.security.AccessController.doPrivileged(Native Method)
          at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:317)
          at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:280)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
          at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:375)

New macbook pro, safari won't open and repair disk permissions did nothing to help

Safari starts, blue bar moves about an inch in search bar, then stops. Then nothing. Tried repairing disk permissions to no avail. Safari still doesn't open. Whatever os x that is installed on new macbook pro's, since just bought on Sunday 10-14-12, is the operating software. The apple store there is no user manual. Strange. So here we are on another, older macbook pro, able to go on internet and see what answers or diagnoses others have tried and trued.

3 days old?, just pack the machine up and tell them you want another one, that this one is a lemon.
They will likely take your word for it and just give you another rather than you demand your money back instead.
If you wait too long then they say you should have brought it back sooner, now have to wait until it's fixed, only to give you more problems later.

I just restarted my mac then suddenly when it boots,disk utility came and says different option like repair disk, get help, reinstall OSX and I tried to click disk repair but it says that I am um able to repair the disk

i just restarted my mac then suddenly when it boots,disk utility came and says different option like repair disk, get help, reinstall OSX and I tried to click disk repair but it says that I am um able to repair the disk

It sounds like your hard drive either has a software problem that Disk Utility cannot fix or that the HD has failed (mechanically).
Your Mac may have booted either to your recovery partition or to internet recovery in an attempt to repair the drive- I can't tell from your post.
I'll assume that it was the recovery partition.
Try to boot into internet recovery (hold down option command R at restart), and see if you can repair your HD with Disk Utility. You should also repair permissions while you're there.
If that doesn't work, try to boot into single user mode (restart, hold down ⌘S until you see a black screen with white text) and repair your hard drive. Here's a reference with directions: Repair Your Hard Disk in Single User Mode | Everything Macintosh
If that doesn't work you have a few options:
If your mac originally came with installation disks, you can try to boot from the installation disk and then see if you can repair the HD.
There is a small chance that Techtool Pro 7 will be able to repair your HD if Disk Utility can't.
If none of that works then your HD has probably failed and will need to be replaced, which is not too difficult to do yourself if you can use a screwdriver.

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

Does anyone know what this Repair Disk Permissions stuff means?

Safari hung on me today, so i decided to repair disk permissions. This text keeps coming up. Is my computer gonna explode or something? Thanks in advance for any help...my OS is 10.6.7
Repairing permissions for “Macintosh HD”
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/dt.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/dt.jar".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jce.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jce.jar".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jconsole.ja r", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jconsole.ja r".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/management- agent.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/management- agent.jar".
User differs on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib", should be 0, user is 95.
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/dt.jar", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/dt.jar".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/jce.jar", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/jce.jar".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/management -agent.jar", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/management -agent.jar".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/security/b lacklist", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/security/b lacklist".
User differs on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Libraries", should be 0, user is 95.
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Libraries".
Permissions differ on "System/Library/Java/Support/Deploy.bundle/Contents/Home/lib/security/cacerts", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/Support/Deploy.bundle/Contents/Home/lib/security/cacerts".
Permissions differ on "System/Library/Java/Support/Deploy.bundle/Contents/Resources/Java/deploy.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/Support/Deploy.bundle/Contents/Resources/Java/deploy.jar".
Permissions differ on "System/Library/Java/Support/Deploy.bundle/Contents/Resources/JavaPluginCocoa.b undle/Contents/Resources/Java/deploy.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/Support/Deploy.bundle/Contents/Resources/JavaPluginCocoa.b undle/Contents/Resources/Java/deploy.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/dt.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/dt.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jce.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jce.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jconsole.jar ", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jconsole.jar ".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/management-a gent.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/management-a gent.jar".
User differs on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib", should be 95, user is 0.
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/dt.jar", should be lrwxr-xr-x , they are -rw-r--r-- .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/dt.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/jce.jar", should be lrwxr-xr-x , they are -rw-r--r-- .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/jce.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/management- agent.jar", should be lrwxr-xr-x , they are -rw-r--r-- .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/management- agent.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/security/bl acklist", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/security/bl acklist".
User differs on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Libraries", should be 95, user is 0.
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Libraries".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle", should be drwxr-xr-x , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle".
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 .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/deploy.jar".
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 .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/libdeploy.jnilib".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/ Contents/Home/lib/security/cacerts", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/ Contents/Home/lib/security/cacerts".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/ Contents/Resources/Java/deploy.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/ Contents/Resources/Java/deploy.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/ Contents/Resources/Java/libdeploy.jnilib", should be -rwxr-xr-x , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/ Contents/Resources/Java/libdeploy.jnilib".
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
Permissions repair complete

Pleasant dreams.
Please note the items listed under Legend in the right sidebar of this page.

Repair disk permissions.SUID issue- Unable to get some applications to load

I need some help in repairing disk permissions ...It is affecting an application I am trying to install (1Password) in which I cannot due to applications being run by user = root.
Below is my disk verification log:
I would appreciate someone walking me through this SUID issue.
I cannot install 1Password app as it is my understanding that the user Root will not allow these permissions.
here is my Disk Verification Log;
Verify permissions for “Hard Disk”
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.
Permissions differ on "private/var/log/secure.log", should be -rw------- , they are -rw-r----- .
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.
Group differs on "Library/PreferencePanes", should be 0, group is 80.
Permissions differ on "Library/PreferencePanes", should be drwxr-xr-x , they are drwxrwxr-x .
ACL found but not expected on "Applications/Utilities".
ACL found but not expected on "Applications".
ACL found but not expected on "Library".
ACL found but not expected on "Library".
Permissions verification complete

Hi gmckay,
The "Waring:SUID file..." messages are only warning message and are not a concern. The SUID bit is supposed to be set on those file. This is a glitch in the installer program- that does not update the installer database with the correct SHA1 digest for those files. The secure.log entry is a glitch in the newsyslog.conf file that sets the permissions on the secure.log less permissive than those recorded in the installer database. The ACL warning messages are caused by another glitch in the installer database. What concerns me are the double ACL messages for "LIbrary". Is this a typo?

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.

When I repair disk permissions I get the following:Repairing permissions for "MacIntosh HD" Determining correct file permissions. Permissions differ on ./Library/Widgets, should be drwxr-xr-x , they are drwxrwxr-x Owner and group corrected on ./Library/W

Repairing permissions for “MacIntosh HD”
Determining correct file permissions.
Permissions differ on ./Library/Widgets, should be drwxr-xr-x , they are drwxrwxr-x
Owner and group corrected on ./Library/Widgets
Permissions corrected on ./Library/Widgets
Permissions differ on ./System/Library/User Template, should be drwx------ , they are drwxr-xr-x
Owner and group corrected on ./System/Library/User Template
Permissions corrected on ./System/Library/User Template
Group differs on ./usr/bin/fetchmail, should be 0, group is 6
Permissions differ on ./usr/bin/fetchmail, should be -rwxr-xr-x , they are -rwxr-sr-x
Owner and group corrected on ./usr/bin/fetchmail
Permissions corrected on ./usr/bin/fetchmail
Permissions differ on ./usr/lib/php/build/Makefile.global, should be -r--r--r-- , they are -r-xr-xr-x
Owner and group corrected on ./usr/lib/php/build/Makefile.global
Permissions corrected on ./usr/lib/php/build/Makefile.global
Permissions differ on ./usr/lib/php/build/acinclude.m4, should be -r--r--r-- , they are -r-xr-xr-x
Owner and group corrected on ./usr/lib/php/build/acinclude.m4
Permissions corrected on ./usr/lib/php/build/acinclude.m4
Permissions differ on ./usr/lib/php/build/mkdep.awk, should be -r--r--r-- , they are -r-xr-xr-x
Owner and group corrected on ./usr/lib/php/build/mkdep.awk
Permissions corrected on ./usr/lib/php/build/mkdep.awk
Permissions differ on ./usr/lib/php/build/phpize.m4, should be -r--r--r-- , they are -r-xr-xr-x
Owner and group corrected on ./usr/lib/php/build/phpize.m4
Permissions corrected on ./usr/lib/php/build/phpize.m4
Permissions differ on ./usr/lib/php/build/scan_makefile_in.awk, should be -r--r--r-- , they are -r-xr-xr-x
Owner and group corrected on ./usr/lib/php/build/scan_makefile_in.awk
Permissions corrected on ./usr/lib/php/build/scan_makefile_in.awk
Permissions differ on ./usr/lib/system/libmathCommon.A.dylib, should be -r-xr-xr-x , they are -rwxr-xr-x
Owner and group corrected on ./usr/lib/system/libmathCommon.A.dylib
Permissions corrected on ./usr/lib/system/libmathCommon.A.dylib
Permissions differ on ./usr/libexec/dumpemacs, should be -r-sr-xr-x , they are -r-xr-xr-x
Owner and group corrected on ./usr/libexec/dumpemacs
Permissions corrected on ./usr/libexec/dumpemacs
Permissions repair complete
The privileges have been verified or repaired on the selected volume
Then I sometimes get the brown screen that states,You must re-start your computer.
I have already zeroed out the hard drive and re-installed Panther and the upgrade Tiger disc.
I repair permissions using the Tiger disc upgrade.
Can anyone help me with this??

> I repair permissions using the Tiger disc upgrade.
One thing to note... When running Repair Disk Permissions, it is best to run it while started up normally, from your normal startup disk, not from a Mac OS X installation disc. The only time you should run it while started up from an installation disc is if some problem is preventing you from starting up normally. OTOH, Repair Disk can only be used when starting up from a different disk (such as an installation disc).
So, I would start up normally, run Disk Utility, and use Repair Disk Permissions on your normal startup disk.
NOTE: Repair Disk Permissions often gives alerts messages that can be ignored. They are more "informational," not serious errors.
http://support.apple.com/kb/TS1448
You should still run it periodically. When you run it, what needs to be repaired has been repaired; consider the rest of it an FYI. I've never experience a problem, where a Repair Disk Permissions message actually caused a problem. But, if you ever get an error while running Repair Disk (or Verify Disk), that is usually a serious problem.

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

Rationale for Repairing Disk Permissions

I repair permissions before and after installations, and I suggest others to do so. However, I have read in some threads in Discussions there there is no technical basis for repairing disk permissions before installation, and that only repairing after installation is necessary.
I realize that there are different opinions about this, but beyond opinions is there a technical basis or rationale for repairing disk permissions before installations?
Thanks.
cornelius
Message was edited by: cornelius

Hi cornelius,
Here is some reading about this topic. Mind that Apple DOES recommend repairing permissions as routine maintenance (see links at the bottom)! My suggestion to Repair permissions before and after an update has a very simple rational: If you forgot to repair permissions AFTER the last update you might get into trouble. Therefore it is safe and costs only a few seconds to do it before and after the update.
mac.column.ted: Unravelling the Repair Disk Permissions controversy
"Ted Landau
May 2006
Repairing Disk Permissions. Not exactly a topic that you would expect to spark much controversy. Yet, surprisingly, it is the focal point of a rather heated debate.
The command itself is innocuous enough. It is included as part of the First Aid component of Disk Utility. Apple's Help for Disk Utility states: "User permissions associated with files, folders, or applications can become damaged and prevent a file or application from opening. Permissions problems can also cause your computer to run slowly. Using Disk Utility, you may be able to fix these permissions problems...Repairing permissions may also be recommended after updating the system or installing new software."
Consistent with this, many users and Web sites (including MacFixIt and at least some postings on MacinTouch) recommend the use of Repair Disk Permissions, not only for specific signs of trouble, but as a part of generic troubleshooting and ongoing maintenance for your Mac.
In contrast, other members of the Mac community (writing in locations such as the Daring Fireball , Unsanity, and the MDJ) argue that running this command just for maintenance, in the absence of any particular symptom, is essentially worthless. Some critics go even further and claim there is no justification for ever selecting to repair permissions. Not only is it useless, they contend, but it may even cause new problems to appear. This viewpoint is often expressed with inflammatory rhetoric such as "covering yourself in Vaseline and rolling around naked in the dirt and repairing permissions are just as likely to fix your Mac OS X problem" (Unsanity).
Regardless of who's right or wrong, I don't believe that insulting users is merited here, especially when these users are simply following advice suggested by Apple itself. As it turns out, I also do not agree with the position of these critics. So, although I may be stepping into a minefield, here's my own take on this subject and my resulting recommendations. [Disclaimer: I was not involved in the authorship of previous MacFixIt articles on this subject. This column is my separate opinion, and does not necessarily reflect the views of MacFixIt.]: Continued"
Mac OS X 10.3 Help: "It's a good idea to repair disk permissions as a regular maintenance task after upgrading or installing new software."
Mac OS X 10.4 Help: "It's a good idea to repair disk permissions as a regular maintenance task after upgrading or installing new software."
Randy B. Singer: Macintosh OS X Routine Maintenance

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

Problem repairing disk permissions

Hey all, I'm trying to help a friend with a sick macbook I think it's a pro, but I definitely know he's running OS 10.5.
I tried to repair his disk permissions in the Disk Utility, and I keep getting the same three messages- "ACL found but not expected in system folder", "ACL found but not expected in Library", and the same thing in one other folder which I forget right now....
I ran the "repair disk permissions" operation three times in a row and keep getting the same three messages. Each running takes about ten minutes and the progress bar hangs at about 15% completion for 90% of the operation. Then in the last minute, it charges across the screen, the operation completes and those messages pop up.
I've never had anything like this happen (when repeated attempts at repairing seemingly don't accomplish the repair of permissions).
Any advice? No other repairs are being logged.

Leopard 10.5 has Access Control Lists enabled and uses them for some of the system folders. The Disk Utility is just informing you that an Access Control List was found, but the information used to repair the permissions doesn't show one. Probably what happened is the "apply to enclosed items" was used from the Get Info window, which added ACLs to the enclosed items. The Get Info window doesn't show extended permissions very well, so applying the permissions to enclosed items shouldn't be used on system files and folders.

Repair disk permissions help

Similar Messages

Maybe you are looking for