Repairing permissions without effect

Hello,
I tried to repair with diskutility and tried to repair with Techtool Pro 5; Three times in succession and every time the report looks like the others.
a
Die Zugriffssteuerungsliste wurde gefunden, jedoch nicht für „private/var/root/Library/Preferences“ erwartet.
German; in english perhaps: The acces-control-list was found, though not expected for.....„“ “
b
Die Zugriffssteuerungsliste wurde gefunden, jedoch nicht für „private/var/root/Library/Preferences“ erwartet.
c
Die Zugriffssteuerungsliste wurde gefunden, jedoch nicht für „private/var/root/Library/Preferences“ erwartet.
a
Die Zugriffsrechte unterscheiden sich für System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CodeResources, Soll-Wert: -rw-r--r-- , Ist-Wert: lrwxr-xr-x .
German; in english perhaps: The permissions differ for ... , the state should read .... , is .....
b
Die Zugriffsrechte unterscheiden sich für System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CodeResources, Soll-Wert: -rw-r--r-- , Ist-Wert: lrw-r--r-- .
c
Die Zugriffsrechte unterscheiden sich für System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CodeResources, Soll-Wert: -rw-r--r-- , Ist-Wert: lrw-r--r-- .
What means the l in front of the notation?
Thank you,
Karl

The acces-control-list was found, though not expected for
That means the item has a list on it which specifies who can do what with it but the repair permissions mechanism wasn't expecting one. Ignore those messages too.
(45367)

Similar Messages

  • My MacBook Pro is running very slow.  I've run repair permissions without positive result.  Does anyone have any ideas?

    My MacBook Pro (2010) is runnign very slow.  This came on all of a sudden.  It opens, closes, reboots, etc., all much slower than ever before.  I have used the repair disk permissions without any positive result.  Does anyone have any ideas?

    First, back up all data immediately, as your boot drive might be failing.
    Take these steps when you notice the problem.
    Step 1
    Launch the Activity Monitor application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Activity Monitor in the icon grid.
    Select the CPU tab of the Activity Monitor window.
    Select All Processes from the menu in the toolbar, if not already selected.
    Click the heading of the % CPU column in the process table to sort the entries by CPU usage. You may have to click it twice to get the highest value at the top. What is it, and what is the process? Also post the values for % User, % System, and % Idle at the bottom of the window.
    Select the System Memory tab. What values are shown in the bottom part of the window for Page outs and Swap used?
    Next, select the Disk Activity tab. Post the approximate values shown for Reads in/sec and Writes out/sec (not Reads in and Writes out.)
    Step 2
    You must be logged in as an administrator to carry out this step.
    Launch the Console application in the same way as above. Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.
    Post the 50 or so most recent messages in the log — the text, please, not a screenshot.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into a message.
    Important: Some personal information, such as your name, may appear in the log. Edit it out before posting.

  • Repair Permissions with/without Tiger disk?

    I was wondering what the best way is to repair permissions. Should one repair them booting off the Tiger disk or can one just open disk utility and repair the permissions while running on their hard drive?
    Also, my new iMac came with two disks. I also have a Tiger disk from when I purchased Tiger for my PowerBook. If it is necessary to repair permissions from the disk, which disk should I use? Can I use the Tiger disk or should I use one of the disks that came with my iMac?
    Thanks!

    Regarding your first question, it makes no difference so there isn't any need to boot from the install disc to repair disk permissions.
    Regarding your second question, the same applies but you should use the Tiger install package that shipped with your new iMac to run repair disk via Disk First Aid when booted from the iMac's install disc on your iMac's boot volume which is much more important than repairing disk permissions.
    The Tiger retail install package is not Universal - it is for a Mac with a PPC processor only and your new iMac has an Intel processor.
    Check this link for system troubleshooting procedures which includes running repair disk, repairing disk permissions and system and user cache cleaning.
    http://www.thexlab.com/faqs/repairprocess.html
    And this link for recommended maintenance for OS X which isn't much focusing on the Maintenance Myths section.
    http://www.thexlab.com/faqs/maintainingmacosx.html
    And this link about running repair disk via Disk First Aid.
    http://www.thexlab.com/faqs/durepairfns.html

  • New Mac Mini and Repairing Permissions

    I've been having trouble with my Mail program and thought I would repair permissions to see if that would help. I ran disk utility from my internal hard drive and ran repair permissions. Apparently it found several permissions to repair, so I thought I would run repair permissions again and the same list appeared. Running a third time and the same list appeared again.Do these permissions ever get repaired? What do I do from here? Should I repair permissions after booting up off of my original system disk? This Mini is only a couple of weeks old and I'm already having problems with Mail and repairing permissions.
    rskover

    Thank you Tim but the computer is packed back waiting for TNT to take it back to Apple. I don't have time to play with permissions, the permissions are OK in the old computer.
    This is what may have been your problem. The permissions on your old computer may not have matched the new computer. I think you gave up before the penny dropped.
    They sell the computers very expensive and I think they would have to improve quality.
    I am unsure how that can be one of your gripes as when the cube came out it was way overpriced in comparison to their other desktops. That did not stop your or I getting one then.
    Your issue was a software problem not a hardware problem so no matter what kind of mac you had it would have needed troubleshooting.
    The quality of the new mac mini far exceeds that of the cube. Try playing 1080P high definition media on your cube, or even 480P for that matter. Try outputting 5.1 surround sound from your cube without the addition of a firewire audio interface.
    I know how frustrating it can be when something just does not seem to work. I have encountered this a few times in my work. However sometimes I just have leave it come back with fresh eyes and try other approaches and I succeed.
    What you need to appreciate installing an upgrade should be planned for any eventuality. In business upgrades are scheduled to have the minimum impact on the workplace. That being said I have worked 48 hrs solid over a weekend getting systems up for a monday morning. They are not always straightforward.

  • Repairing permissions before and after updating software

    What is the reason to repair permissions before and after updating software? This may sound like a stupid question to many of you, but I am new to computers and I am trying to learn how and why of some of the things of my PowerBook. I installed some updates without repairing permissions. Did I install some software updates the wrong way? Thank you.

    This is a topic which will draw as many emphatic for and against responses as overnight shut down or not, defrag or not, optimise or not, and so on.
    I agree with Neil. I believe that OS X has progressed sufficiently that repair permissions has become redundant and so I do not do it on any regular basis.
    Some folk may refer you to an Apple Support Article 303602. That Article in its 4 May 2006 version, titled "Top 10 Tips to Keep Your Mac in Top Form" suggested Repair Permissions should be done "after upgrading or installing new software". The Article was however revised on 15 May 2006 to be titled "Top Tips to Keep Your Mac in Top Form" and the item on Repair Permissions [along with two other recommended maintenance tips] was removed. It is my view that the conclusion to be drawn here is that Apple no longer considers Repair Permissions to be a required maintenance procedure.
    Many users have adopted a "Repair Permissions" mantra for a cure-all over several years. I dropped it sometime in 10.3.
    But, to each his own.
    HTH
    TiPB 867   Mac OS X (10.4.6)  

  • Disk utility - repair permissions keeps reporting same issues

    my machine has been unstable for a while, and i thought it was time to repair permissions.
    normally, after being run a couple of times, there are no more to be repaired. however, this time, the same 35 lines of permissions being changed are displayed over and over. also after rebooting.
    1. why aren't the permissions finally corrected?
    most issues concern 'System/Library/CoreServices/Front Row.app/Contents', 'System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins' and a couple of warnings that suid-files are changed and won't be repaired.
    2. i never used front row, - what's happening?
    3. what's with the suid-files?
    4. will reinstalling leopard help my situation?
    5. if i use time machine to restore, how can i be sure the problems don't persist? or 'get back in'?

    why aren't the permissions finally corrected?
    Apple changed the structure of some of its packages without updating the repair permissions mechanism. Until and unless they release a patch, nothing done will stop those messages from appearing. Disregard them.
    i never used front row, - what's happening?
    You installed a package which updated it.
    what's with the suid-files?
    Those messages are normal.
    (43205)

  • Please Help, After Kernel panic restart failed- apple swirl(6 hrs), SafeMode-failed, SUMode-sucess. Could not unmount disk to erase. Repair permissions-multiple fail errors:unable to set permissions on... unable to set owner and group...

    Please Help, I deleted an account that was the same name as the administrator but was not the administrator. Also a samsung galaxy s phone was charging through the usb port.
    I closed out a program and got a message that the temp file could not be stored/saved.
    Then a Kernel panic message occurred and restart was necessary.
    The restart resulted in the screen with the apple logo and a continous swirl for 6+hrs,
    Attempted Safe Mode start up, unsuccessful,
    Single User Mode-sucess.
    Ran $ fsck_hfs -rfd /dev/disk0s2 Ran several times repairs made with one which remained. something about a node.
    No change in start up attempts
    Started with install CD matching current OS 10.6
    Ran Disk Utility Repair Permissions resulting in multiple errors:
    One line/error
    Warning: SUID file /////Ardagent has been modified and will not be repaired
    144 lines/errors of this type of series of lines
    Group permissions differ on...should be drwxr-xr-x, they are -rw-r--r-- .
    permissions differ on...should be drwxr-xr-x, they are -rw-r--r-- .
    unable to set owner and group...error 22: Invalid Argument
    unable to set permissions on...error 22: Invalid Argument
    Ran Repair Disk, result:
    Error: Could not unmount disk (in red)
    Ran Verify Disk, result:
    The volume HD appears to be ok (in green)
    Next I attempted to erase the dist to start from scratch since I have data backed up on time machine.
    Error message box
    Volume Erase failed
    Volume Erase failed with error:
    Could not unmount disk
    I am looking to solve without buying DiskWarrior unless only resort.

    So it looks like  solved it for now I will update later. What I did was after starting from the install cd for the 10.6 system I ran from terminal ran:
    diskutil disablejournaling /dev/disk0s2
    diskutil disableownership /dev/disk0s2
    diskutil repairPermissions /dev/disk0s2
    then i closed terminal and then when to disk utility and chose to repair disk with results all was fine. Then ran repair permissions and got similar results from terminal function next I erased disk and then chose to restore from time machine and it is now restoring! yea!

  • Verifying and Repairing Permissions on Mac OS X 10.5 giving many errors

    I am having a problem with verifying and repairing my permissions. I first noticed this yesterday and thought it was some kind of application conflict so I wiped my HDD via zero data and reinstalled OS 10.5 then upgraded to OS 10.5.1. Without installing any applications other than those that were installed via the CD and the update, I rechecked my "Repair Permissions" and got the following:
    Quote
    Verifying volume “MacMini”
    Performing live verification.
    Checking Journaled HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Checking multi-linked files.
    Checking Catalog hierarchy.
    Checking Extended Attributes file.
    Checking volume bitmap.
    Checking volume information.
    The volume MacMini appears to be OK.
    Verify permissions for “MacMini”
    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.
    Unquote
    This appears to be a bug in the OS. Has anyone else had this problem. It has only occurred since I upgraded to Leopard from Tiger. Any ideas anyone?

    Click here for information, and run this update to get rid of many of the messages.
    (28455)

  • Warning messages after repairing permissions

    I hope that someone out there can tell me what these messages mean after running Disk Utility on my new MBP. Here is what it says:
    Repairing permissions for “Mac HD”
    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.
    ACL found but not expected on "System/Library/User Template/English.lproj/Sites".
    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.
    ACL found but not expected on "System/Library/User Template/English.lproj/Desktop".
    ACL found but not expected on "System/Library/User Template/English.lproj/Documents".
    ACL found but not expected on "System/Library/User Template/English.lproj/Downloads".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Application Support".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Assistants".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/MIDI Drivers".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Plug-Ins/Components".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Plug-Ins/Digidesign".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Plug-Ins/VST".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Plug-Ins".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Sounds/Alerts".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Sounds/Banks".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Sounds".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/ColorPickers".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Compositions".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Favorites".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/FontCollections".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Fonts".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/iMovie/Plug-ins".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/iMovie/Sound Effects".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/iMovie".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Input Methods".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Internet Plug-Ins".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Keyboard Layouts".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Preferences".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Printers".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Screen Savers".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Sounds".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Voices".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library".
    ACL found but not expected on "System/Library/User Template/English.lproj/Movies".
    ACL found but not expected on "System/Library/User Template/English.lproj/Music".
    ACL found but not expected on "System/Library/User Template/English.lproj/Pictures".
    ACL found but not expected on "System/Library/User Template/English.lproj/Public".
    Warning: SUID file "Applications/Utilities/Keychain Access.app/Contents/Resources/kcproxy" has been modified and will not be repaired.
    Permissions repair complete

    It sounds like you used the 10.5.1 update using Software Update.
    Download the larger 110MB file of 10.5.1 directly from Apple and this will most likely take care of all but one SUID warning.
    http://www.apple.com/support/downloads/macosx1051update.html
    The remaining warning is normal and will cause no problems.

  • Repairing permissions gives me tons of errors

    I've been having trouble opening some apps (i.e Activity Monitor) so I figured I should repair my permissions. When I do so, I get a HUGE amount of errors, I'll include just a very small portion of them below.
    Any idea how to fix it?
    Thanks!
    Repairing permissions for “Mac OS X”
    Determining correct file permissions.
    Permissions differ on ./Applications/Address Book.app/Contents/MacOS/Address Book, should be -rwxrwxr-x , they are -rwxr-xr-x
    Owner and group corrected on ./Applications/Address Book.app/Contents/MacOS/Address Book
    Permissions not corrected on ./Applications/Address Book.app/Contents/MacOS/Address Book, reason Operation not permitted
    Permissions differ on ./Applications/Address Book.app/Contents/Resources/MailInviteBundle.bundle/Contents/MacOS/MailInviteBu ndle, should be -rwxrwxr-x , they are -rwxr-xr-x
    Owner and group corrected on ./Applications/Address Book.app/Contents/Resources/MailInviteBundle.bundle/Contents/MacOS/MailInviteBu ndle
    Permissions not corrected on ./Applications/Address Book.app/Contents/Resources/MailInviteBundle.bundle/Contents/MacOS/MailInviteBu ndle, reason Operation not permitted
    Permissions differ on ./Applications/Address Book.app/Contents/Resources/Telephony.bundle/Contents/MacOS/Telephony, should be -rwxrwxr-x , they are -rwxr-xr-x
    Owner and group corrected on ./Applications/Address Book.app/Contents/Resources/Telephony.bundle/Contents/MacOS/Telephony
    Permissions not corrected on ./Applications/Address Book.app/Contents/Resources/Telephony.bundle/Contents/MacOS/Telephony, reason Operation not permitted

    There is also this article on resolving permissions issues:
    http://docs.info.apple.com/article.html?artnum=106712
    As for your question about reinstalling without losing preferences, yes, it is called an Archive and Install:
    http://docs.info.apple.com/article.html?artnum=301270
    None, if you upgraded Mac OS X since you initially got the machine, it is more difficult to archive and install, as newer applications may not work right with the older operating system.
    I would still though backup your data before doing it as my FAQ explains:
    http://www.macmaps.com/backup.html
    Even a corrupted backup is better than none, as critical data files can be rescued if there is an issue.

  • OS X 10.6.7 Canon All-in-One 480 Printer will not print files, only blank pages. Have to go to Utilities, Disk Utility  and Repair permissions for a temporary fix. How can I get a permanent fix?

    After upgrading to OS X 10.6.7., my Canon All-in One MP 480 printer will not print. it says it is printing, but the sheet of paper just runs through the printer and comes out blank. I finally went online to just answers.com and got a fix involving the System preferences, printer and fax. i was told to go to Applications in the HD, thenUtilities, then Disk Utilities, highlight the HD and check on Verify Disk. If it says Disk is OK, click on Repair Permissions. At first, that worked, but the next time I went to print after turning the printer off, it refused to print and just ran the sheet of paper through blank. Once that happens, there is no way to go back to printing the file that failed. I fiinally had to copy and paste the info from the file that would not print and put it in an email to myself and then print that. This is very frustrating, and I would really like a final solution for the problem.
    bettyfroomneedham

    There's a lot there, so I'll start with the parts I can answer quickly.
    The "ACL found but not expected..." messages can be safely ignored, so says this article
    http://docs.info.apple.com/article.html?artnum=306925
    (look below all the "SUID" examples)
    I had changed my Desktop image earlier but when the "Installing 1 item" window came up it changed back to the back ground that you first see on your desktop after installation.
    Leopard installs updates a bit differently. If it's simply an application that does not change system files, it installs them like before, without having to restart. If the update is to the system, then you must immediately "restart," It then goes to that stars and purple screen to perform the installation. Before, it would do the installation while you still had control of the Mac and would prompt you to restart when it finished the installation. This change probably make things more secure and reliable, because you aren't allowed to do other things on the Mac while system updates are being installed.
    Please post back with the remaining point of concern.

  • After repairing permissions, do I need to "verify"?

    Hi folks,
    I'm trying to get iDVD working; I keep getting a multiplexing error and the disk ejects when I try to burn a DVD. It was suggested I repair permissions, which I did. However, I was then presented with an option to "verify" the repairs to permissions. Is this a necessary step in repairing permissions?
    Thanks very much.
    FYI: When I repaired permissions the first time, I didn't verify and iDVD still won't burn a DVD. I'm just wondering if "verifying" would help.
    Thanks again,
    Vic

    How does the particular user account affect burning a DVD?
    That suggestion is to check whether there is an error on a particular user account. If it doesn't show up in another account, there is.
    now I have about 90 GB of free space
    Then we can rule that out!
    I'm using Fuji disks, which I've burned to before without any problems
    Yep, they are usually trouble free.
    I'm even using a short, stand-alone .mov file (exported from FCE4)
    That could be a hint. Is it in widescreen?
    iDVD: DV widescreen 16:9 workflow from Final Cut Pro
    http://support.apple.com/kb/TS2179?viewlocale=en_US
    Final Cut Express: DV widescreen 16:9 workflow for iDVD at http://support.apple.com/kb/TS1611
    and
    Preparing your Final Cut Express or Final Cut Pro movie to work with iDVD at http://docs.info.apple.com/article.html?path=iDVD/7.0/en/6652.html
    Is there a sure-fire way for me to check whether there's a problem with my Superdrive?
    You could trry cleaning it using a standard CD/DVD lens cleaner using tiny brushes. Or try burning something else (a different project perhaps) to see if that works.
    I think it was during something called "Creating Lead-in" or something like that? and says something that includes the words, "...media error"
    We may be getting warmer. Could be dud DVD. Try another.
    Post back with results!

  • Help re repairing permissions

    Hi all, I hope I'm posting this in the right forum! i like many of us have just upgraded to Leopard with little or no difficulty. However last night before shutting down my MP i decided to repair permissions to ensure everything was still okay as it was a new O/S. On completing "Verify permissions I was given the following information:
    Warning: SUID file "System/Library/CoreService/RemoteManagement/ARDAgent" has been modified and will not be repaired.
    Has anyone had the same message?
    Does anyone know what it means?
    Do I need to take any action? if so what would you suggest?
    As I said earlier everything seems okay, and Time machine is backing up to my D2 Quadra external HD via Firewire 800 without issue. Your advice and guidance would be very much appreciated re this issue as I'm not sure how to proceed.
    Thanks in anticipation of your valued help,
    Denis

    I found the same thing when when repairing permissions after noticing the slow boot up I have with Leopard and the taskbar taking so long to render. I was a little paranoid at first, but I am more at ease now.
    Thanks for the post

  • Leopard: Repair Permissions - Installdb - massive memory usage!

    It's been known for a while now that the disc utility isn't running up to snuff on leopard. There was a recent update that now allows the time-bar to run, showing you how long you have to wait 'till done (which was definitely a fix from there being no time-bar at all). However, I'm finding a very strange thing occurs when I try to repair permissions.
    Simultaneously as I tried repairing, I ran the activity monitor to see what the processes looked like on my ram (I'm operating on 512, which I know is a bit low for the new OS). What I found was that there's a process name called installdb, that was going haywire. When I began to repair the permissions, the installdb process was using less than a dozen mb of ram, within minutes my cpu was heating up super-fast, and I found this installdb was sucking up more and more ram, until finally the process shut down (of its own accord?) at 220 MB of ram used.
    Of course my page in-out count got super high at that point because I'm only using 512 to begin with, but I just have to think that something in the installdb process is responsible for the difficult times with disc repair.
    As well, while the new update solved one particular permission issue (already discussed, SUID file), it seems to have left many more in its wake. I get the following list of messages now from repair disc, and this list has not changed, despite having repaired permissions 3 times in the last 2 days.
    Anyone have a heads up on either the installdb process, or the below-listed repair issues?
    Permission repair issues:
    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.
    Thanks a ton,
    ZenChess

    PS: I notice that after the permissions repair was complete, my activity monitor went from an average of 230 MB's of free ram, to 305. So it looks like the repair permissions did have an effect, although the messages left behind said no repairs went into effect.
    Totally confused,
    ZenChess

  • Can't repair permissions

    Any ideas why I can't repair permissions? I've installed 10.5 on my 12" 1.33ghz Powerbook and since installing I haven't been able to repair permissions. I'm trying to use disk utility without having to reboot. It will start but it just spins for ever. It never does anything. Doesn't show progress and it never stops.

    I had the same problem. But I was stupid enough to hit the powerbutton when i thought my computer froze..
    The consequence was that when my mac restarted, and my keyboard didnt work anymore, except for the num-lock option, so i could type numbers..
    I dont know very much about computers, but i can tell you that repair permission doesnt work like it ought to. I had to do a leopard clean install after that and I haven't tried the repair permission after that.
    Think we'll have to wait untill apple comes with an update..

Maybe you are looking for