Repair Disk Permissions same results three times

On my Mac Book (running 10.5.8)  Safari started to quit unexcpetitily. So I ran the Repair Permissions restarted my machine ran it again and got the same results from the repair permissions.  Hmm thats odd. So I booted into "Single User" Mode and ram fsck -y everything was OK there. Booted back into the OS and ran Repair Permissions again Same Permissions came back as fixed again. Hmm..  Here they are:
Repairing permissions for “Macintosh HD”
          Reading permissions database.
          Reading the permissions database can take several minutes.
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Menu Extras/RemoteDesktop.menu/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "System/Library/Frameworks/AppKit.framework/Versions/C/_CodeSignature/CodeResou rces", should be ?--------- , they are ---------- .
Permissions differ on "System/Library/PrivateFrameworks/DotMacSyncManager.framework/Versions/A/_CodeS ignature/CodeResources", should be ?--------- , they are ---------- .
Permissions differ on "System/Library/PrivateFrameworks/DotMacSyncManager.framework/Versions/A/Resour ces/DotMacSyncHelper.app/Contents/_CodeSignature/CodeResources", should be ?--------- , they are ---------- .
Permissions differ on "System/Library/PrivateFrameworks/DotMacSyncManager.framework/Versions/A/Resour ces/dotmacsyncui.app/Contents/_CodeSignature/CodeResources", should be ?--------- , they are ---------- .
Permissions differ on "System/Library/PrivateFrameworks/DotMacLegacy.framework/Versions/A/_CodeSignat ure/CodeResources", should be ?--------- , they are ---------- .
Permissions differ on "System/Library/Extensions/IOUSBMassStorageClass.kext/Contents/_CodeSignature/C odeDirectory", should be ?--------- , they are ---------- .
Permissions differ on "System/Library/Extensions/IOUSBMassStorageClass.kext/Contents/_CodeSignature/C odeResources", should be ?--------- , they are ---------- .
Permissions differ on "System/Library/Extensions/IOUSBMassStorageClass.kext/Contents/_CodeSignature/C odeSignature", should be ?--------- , they are ---------- .
Permissions differ on "System/Library/SystemProfiler/SPDisplaysReporter.spreporter/Contents/_CodeSign ature/CodeResources", should be ?--------- , they are ---------- .
Permissions repair complete
Thanks for the help on this one
Thanks

As long as the report ends up with 'Permissions repair complete' then, as far as permissions go, you are fine. You can ignore the various statements in the report:
Permissions you can ignore on 10.5 and 10.6:
http://support.apple.com/kb/TS1448
Using 'should be -rw-r--r-- , they are lrw-r--r--' as an example, you will see the that the permissions are not changed, but the | indicates a different location. This is because an update to Leopard changed the location of a number of system components.
Poster rccharles has provided this description of what it all means:
drwxrwxrwx
d = directory
r = read
w = write
x = executeable program
drwxrwxrwx
|  |  |
|  |   all other users not in first two types
|  | 
|  group
| 
owner
a little more info
Before the user had read & write. A member of the group had read.
After, only the user had read & write.
If you are running Panther or Tiger:
http://support.apple.com/kb/TA21090

Similar Messages

  • Repair Disk Permissions getting busy with time

    When my PowerBook was newer (8 months ago to 2 months ago), permissions repair rarely returned much in the info display window. Now it gives many lines of permission corrections. Often repeating the same ones. For example it often repairs many items in the Resource folder of the Apples DVD player. [ie. - We are using special permissions for the file or directory ./Applications/DVD Player.app/Contents/Resources/English.lproj/AboutBox.nib/objects.xib. New permissions are 33204]. Always the same permissions. It will display these same corrections upon immediately rerunning the repair from Disk Utility. When the PB was new, ran OSX 10.4.1. Now up to OSX 10.4.4
    Most other repairs are Widgets. Many of which I have not used. Thus I have been deleting them.
    Why should the content of the DVD player resource folder get constant permission repair attention?
    Harmz

    You can safely ignore all of the "We are using special permissions...." messages. They are not errors.
    There have been a lot more than with 10.4.0 but they don't mean there is a problem.
    It looks bad, but it's not. There is an Apple KB article that explains it further (it needs to be updated to include the Widget, iDVD and any other lines that say "using special permisisons" but the idea is the same.
    http://docs.info.apple.com/article.html?artnum=107298

  • Repair Disk Permissions with Lion

    Installed Lion two days ago and thought I would "Verify/Repair Disk Permissions" for the first time with Lion. But I'm getting the warning message:
    Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.
    I tried "Repair" twice and got the exact same message both times. I'm not sure if this is serious or not, and can't say for certain if it wouldn't have happened a week ago or few weeks ago (it's been nearly two months since last "Verfiy/Repair"). Any lessons, tips, instructions will be appreciated.

    Installed Lion on my 27" iMac (mid 2010) and everyday since it shuts down after start up.
    Called Apple they said repair permissions, after safe boot. Thats works but only for the next restart.
    When I shutdown and start up the next day I have to go thru the same process.
    Anybody else have this problem?

  • Need to Repair Disk Permissions Everyday? Same errors each time.

    I have a White MacBook 4,1 - 2.1 Ghz 3 MB Cache, 800 MHz Bus. It seems like I need to repair the permissions everyday. Every time I do I get the exact same errors, when I start up off the Mac OS X dvd I get no errors under repair disk, but the same errors under repair permissions.
    This is what I get:
    Repairing permissions for “Macintosh HD”
    Reading permissions database.
    Reading the permissions database can take several minutes.
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/RawCamera.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "Applications/iTunes.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
    Permissions differ on "Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/ CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
    Permissions differ on "Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/CodeResou rces", should be -rw-rw-r-- , they are lrw-rw-r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iLifeMediaBrowser.framework/Versions/A/CodeRe sources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/CodeResourc es", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/BlackAndWhiteEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/CubeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/DissolveTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/DropletTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/FadeThroughBlackTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/FlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/MosaicFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/MosaicFlipTransitionSmall.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/PageFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/PushTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/RevealTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/SepiaEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/TwirlTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/WipeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions repair complete
    Anyone know what's wrong?

    There is no error. You could repair permissions continuously and these same notifications will show up.
    Recent updates to iPhoto, Front Row, and an update for RAW compatibility have resulted in these permissions differences. Rather than replacing the old permissions with a new one, the system sees a symbolic "link" (the L you see in front of the permissions).
    Nothing is wrong with your machine--we're all getting these notifications. Hopefully a system update will change the permissions for us in the future.
    ~Lyssa

  • How to repair disk permissions inside Time Machine?

    I need to restore my .sites file for iWeb from Time Machine, but when I try I get the following error:
    "The operation can't be completed because you don't have permission to access some of the items." What IS restored are a few (10 or so) .jpg files that were part of my site that once contained thousands of pictures, dozens of movies, and three years of work. The file details inside Time Machine ("Quick View") is 972MB, but again -- what is actually restored is only about 10 pics of a mb each.
    Does anyone know how to repair disk permissions for a file inside Time Machine? In Disk Utility the button to repair permissions is grayed out when I select Time Machine volume.
    Much thanks in advance!

    I have the same issue (and circumvented it by copying the files with "cp" from the unix shell). The permissions on the TM disk don't really look wrong, and the fact that I can copy the files means that they aren't read protected.
    There seems to be some serious bug in Time Machine here, my guess is that the TM restore operation somehow does things in the wrong order (like copying with preserved access lists to a temporary location and then try to move the files from there. This won't work since the files will be protected with access lists from accidental removal on the TM disk).
    More discussion in this thread:
    http://discussions.apple.com/thread.jspa?threadID=2164188

  • Repairing disk permissions keeps giving same message

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

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

  • "Repair Disk Permissions" keeps showing the same permission differences

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

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

  • 20 minutes to Repair Disk Permissions.  Every time.

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

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

  • Can't repair disk permissions

    I just bought a new Mac Mini (2.0 GHz Core Duo w/2 GB of RAM and 320 GB HD) and migrated all of my files over to it from my Time Machine Backup. Over the past two days my two external hard drives have developed permission problems. Yesterday, I booted my computer and my Time Machine backup drive (Western Digital 1 GB) had a small lock on the desktop icon and my permissions were all messed up. I had two versions of my account with "custom" permissions and "Staff" and "Everyone" also with "custom" permissions. I couldn't fix it, so I formatted the drive and now it is working.
    Today my other external drive (don't remember maker, 500GB) is doing the same thing (lock on icon, et al), but I don't want to erase it. I tried going to Disk Utility and the verify and repair disk permissions buttons are greyed out. Now, I can't get to my iTunes content on that drive.
    Any help would be appreciated.
    Thanks,
    - Paul

    Called Apple Support three times with less than lousy results. My Mac Mini crashed on my first call and it took three Leopard installs before I got back to where I was to begin with.
    However, none of the technicians would touch Terminal to fix this issue, but I had found instructions all over the Web. So, I ran some of the commands in Terminal and magically I could fix my permissions on the external HD. I am now repairing permissions on my Macintosh HD and hopefully that will be the end of it.
    Phew!

  • 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

  • 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.

  • 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 Boosts Speed

    I had a problem similar to another thread on this forum regarding the spinning beach ball. I was seeing this happen mostly when connecting to the Internet on Safari, but did see it sometimes on iTunes, iPhoto, and even Mail. After I ran Disk Utility, and had it repair disk permissions, eventually the speed problems started to go away. No spinning beach ball.
    Can anyone explain why repairing disk permissions is the be all, end all solution? Why would disk permissions get corrupted in the first place?

    There are many situations where problematic permissions can result in poor system performance, producing the spinning beachball, application or system crashes, freezes, unexpected quitting etc.
    If software were a simple, single, executable file, permissions might not be so critical, but in reality, each application is a collection of components, loaded and executed or opened and read at appropriate times as the software itself is running. You can see some of these components if you right-click on an application icon and select 'show package contents' from the contextual menu - you'll then see a number of folders and files which are part of the app itself. There are other files too - library files - which applications have to have access to and which are 'prebound' to the application to help it run efficiently.
    Since each of these components are crucial to the application, it is inevitable that if any have the wrong permissions, it can affect the ability of the software to read/open/execute the file. In many cases you might not notice any difference, but in others, the spinning beachball or a software crash would be expected.
    Repairing permissions causes MacOs to run through it's system-level files and ensure that ownership and access rights for each is set correctly, thus resolving these issues.
    Permissions can get messed by a number of things - not least being that the same file may be shared between applications and permissions thus set correctly for one but not the other, by installation of software or an update etc which overwrites a file or alters permissions for it, by some utilities or applications which do not entirely conform to the appropriate programming guidelines and thus alter files or permissions in ways that MacOS doesn't recognize, or just by simple error!
    There's an excellent article on the subject you may find interesting at http://www.macworld.com/2006/08/secrets/repairpermissions/index.php?pf=1

  • Constantly having to repair disk permissions after hanging system

    From the time I purchased this I've had ongoing issues with the java, flash, OS updates causing the computer to hang forever. Sometimes I end up having to press the off button because Command Q and Command/Option/Escape won't allow a force quit even after a 20 minute wait. I don't know enough about what's going on behind the boot up to know what's wrong. Here is a copy of my console log and this is exactly what they look like each time after I have gone in and done a disk verify, (says it's okay) and then repair disk permissions. I've had to boot to safe mode 3 times today and repair permissions due to this issue. There is nothing plugged into the computer except the power cord. The OS is up to date per Software Update and the only 3rd party software installed is SKYPE ...
    1/25/11 5:45:58 PM SoftwareUpdateCheck[520] Checking for updates
    1/25/11 5:45:58 PM storeagent[524] port created
    1/25/11 5:46:27 PM com.apple.launchd[1] (com.apple.suhelperd[522]) Exited with exit code: 2
    1/25/11 5:46:27 PM com.apple.launchd.peruser.501[88] ([0x0-0x3d03d].SoftwareUpdateCheck[520]) Exited with exit code: 102
    1/25/11 8:21:42 PM [0x0-0x52052].com.skype.skype[613] Main starting with pid 613 parent pid 88
    1/25/11 8:21:43 PM Skype[613] SkypeApplication::init called
    1/25/11 10:56:56 PM com.apple.launchd[1] * launchd[1] has started up. *
    1/25/11 11:09:29 PM com.apple.fontd[70] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/25/11 11:09:31 PM com.apple.WindowServer[72] Tue Jan 25 23:09:31 Troy-Lindstroms-MacBook.local WindowServer[72] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/25/11 11:09:32 PM com.apple.fontd[70] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/25/11 11:09:40 PM com.apple.UserEventAgent-LoginWindow[79] ALF error: cannot find useragent 1102
    1/25/11 11:09:40 PM com.apple.UserEventAgent-LoginWindow[79] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/25/11 11:09:40 PM com.apple.launchd.peruser.501[90] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/25/11 11:09:42 PM fontd[100] Database content version mismatch (stored(15) != expected(14))
    1/25/11 11:09:47 PM com.apple.launchd.peruser.501[90] (com.apple.Kerberos.renew.plist[108]) Exited with exit code: 1
    1/25/11 11:10:09 PM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
    1/25/11 11:10:12 PM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
    1/25/11 11:10:13 PM com.apple.launchd.peruser.501[90] (com.apple.AirPortBaseStationAgent[110]) Exited: Killed
    1/25/11 11:10:14 PM com.apple.loginwindow[22] shutdown: / is busy updating; waiting for lock
    1/25/11 11:10:33 PM com.apple.launchd[1] * launchd[1] has started up. *
    1/25/11 11:11:24 PM com.apple.UserEventAgent-LoginWindow[81] ALF error: cannot find useragent 1102
    1/25/11 11:11:24 PM com.apple.UserEventAgent-LoginWindow[81] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/25/11 11:11:24 PM com.apple.launchd.peruser.501[90] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/25/11 11:11:28 PM fontd[101] Database content version mismatch (stored(15) != expected(14))
    1/25/11 11:11:28 PM fontd[101] Failed to open read-only database, regenerating DB
    1/25/11 11:11:34 PM com.apple.launchd.peruser.501[90] (com.apple.Kerberos.renew.plist[111]) Exited with exit code: 1
    1/25/11 11:11:40 PM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/25/11 11:11:48 PM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/25/11 11:11:49 PM [0x0-0x9009].com.skype.skype[116] Main starting with pid 116 parent pid 90
    1/25/11 11:11:51 PM Skype[116] SkypeApplication::init called
    1/25/11 11:38:12 PM com.apple.WindowServer[69] Tue Jan 25 23:38:12 Troy-Lindstroms-MacBook.local WindowServer[69] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/26/11 11:36:13 AM [0x0-0x6d06d].com.skype.skype[666] Main starting with pid 666 parent pid 90
    1/26/11 11:36:14 AM Skype[666] SkypeApplication::init called
    1/26/11 12:25:04 PM com.apple.launchd.peruser.501[90] ([0x0-0x6d06d].com.skype.skype[666]) Exited: Terminated
    1/26/11 5:45:58 PM SoftwareUpdateCheck[867] Checking for updates
    1/26/11 5:45:58 PM storeagent[870] port created
    1/26/11 5:47:17 PM com.apple.launchd[1] (com.apple.suhelperd[869]) Exited with exit code: 2
    1/26/11 5:47:17 PM com.apple.launchd.peruser.501[90] ([0x0-0x92092].SoftwareUpdateCheck[867]) Exited with exit code: 102
    1/26/11 8:32:58 PM [0x0-0x11011].com.apple.Safari[143] Wed Jan 26 20:32:58 Troy-Lindstroms-MacBook.local Safari[143] <Error>: unknown error code: invalid drawable
    1/26/11 8:32:58 PM [0x0-0x11011].com.apple.Safari[143] Wed Jan 26 20:32:58 Troy-Lindstroms-MacBook.local Safari[143] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/26/11 8:33:10 PM [0x0-0x11011].com.apple.Safari[143] Wed Jan 26 20:33:10 Troy-Lindstroms-MacBook.local Safari[143] <Error>: unknown error code: invalid drawable
    1/26/11 8:33:24 PM [0x0-0x11011].com.apple.Safari[143] Wed Jan 26 20:33:24 Troy-Lindstroms-MacBook.local Safari[143] <Error>: unknown error code: invalid drawable
    1/26/11 10:48:32 PM com.apple.launchd.peruser.501[90] ([0x0-0x11011].com.apple.Safari[143]) Exited: Terminated
    1/26/11 10:49:37 PM com.apple.launchd[1] (com.apple.suhelperd[1047]) Exited with exit code: 2
    1/26/11 10:49:44 PM com.apple.launchd.peruser.501[90] (com.apple.AirPortBaseStationAgent[113]) Exited: Killed
    1/27/11 11:39:52 PM com.apple.launchd[1] * launchd[1] has started up. *
    1/27/11 11:40:14 PM com.apple.launchd.peruser.501[84] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/27/11 11:40:15 PM com.apple.UserEventAgent-LoginWindow[77] ALF error: cannot find useragent 1102
    1/27/11 11:40:15 PM com.apple.UserEventAgent-LoginWindow[77] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/27/11 11:40:15 PM SoftwareUpdateCheck[98] Checking for updates
    1/27/11 11:40:15 PM com.apple.launchd.peruser.501[84] (com.apple.Kerberos.renew.plist[111]) Exited with exit code: 1
    1/27/11 11:40:17 PM storeagent[119] port created
    1/27/11 11:40:21 PM com.apple.WindowServer[65] Thu Jan 27 23:40:21 Troy-Lindstroms-MacBook.local WindowServer[65] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/27/11 11:40:27 PM [0x0-0xa00a].com.skype.skype[116] Main starting with pid 116 parent pid 84
    1/27/11 11:40:29 PM Skype[116] SkypeApplication::init called
    1/27/11 11:41:02 PM SoftwareUpdateCheck[98] Downloading "iTunes"
    1/27/11 11:42:35 PM SoftwareUpdateCheck[98] Auto-download of "iTunes" SUCCESSFUL.
    1/27/11 11:42:35 PM SoftwareUpdateCheck[98] Launching app
    1/27/11 11:43:20 PM com.apple.launchd.peruser.501[84] ([0x0-0x6006].SoftwareUpdateCheck[98]) Exited with exit code: 102
    1/28/11 9:51:59 AM com.apple.RemoteUI[589] CoreAnimation: rendering error 501
    1/28/11 9:52:15 AM com.apple.RemoteUI[589] HTTP2 Streaming Reads ON
    1/28/11 11:31:15 AM com.apple.launchd.peruser.501[84] ([0x0-0x10010].com.apple.Safari[134]) Exited: Terminated
    1/28/11 11:42:21 AM com.apple.launchd[1] (com.apple.suhelperd[104]) Exited with exit code: 2
    1/28/11 3:49:50 PM com.apple.launchd.peruser.501[84] (com.apple.AirPortBaseStationAgent[113]) Exited: Killed
    1/28/11 3:49:50 PM com.apple.launchd.peruser.501[84] ([0x0-0x80080].com.apple.iTunesHelper[764]) Exited: Killed
    1/28/11 3:50:10 PM com.apple.launchd.peruser.501[84] (com.apple.Dock.agent[88]) Exit timeout elapsed (20 seconds). Killing
    1/28/11 3:53:36 PM com.apple.launchd[1] * launchd[1] has started up. *
    1/28/11 3:55:16 PM com.apple.launchd.peruser.501[90] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/28/11 3:55:16 PM com.apple.UserEventAgent-LoginWindow[82] ALF error: cannot find useragent 1102
    1/28/11 3:55:16 PM com.apple.UserEventAgent-LoginWindow[82] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/28/11 3:55:25 PM com.apple.launchd.peruser.501[90] (com.apple.Kerberos.renew.plist[111]) Exited with exit code: 1
    1/28/11 3:55:27 PM com.apple.WindowServer[72] Fri Jan 28 15:55:27 Troy-Lindstroms-MacBook.local WindowServer[72] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/28/11 3:55:40 PM [0x0-0x8008].com.skype.skype[115] Main starting with pid 115 parent pid 90
    1/28/11 3:55:41 PM Skype[115] SkypeApplication::init called
    1/28/11 11:40:16 PM SoftwareUpdateCheck[419] Checking for updates
    1/28/11 11:40:16 PM storeagent[422] port created
    1/28/11 11:40:59 PM com.apple.launchd[1] (com.apple.suhelperd[421]) Exited with exit code: 2
    1/28/11 11:40:59 PM com.apple.launchd.peruser.501[90] ([0x0-0x56056].SoftwareUpdateCheck[419]) Exited with exit code: 102
    1/29/11 3:02:24 AM quicklookd[551] [QL] 'Creating thumbnail' timed out for '<QLThumbnailRequest /Users/troylindstrom/Downloads/images-30.jpeg>' (Start date: 2011-01-29 03:02:04 -0800)
    1/29/11 3:05:11 AM quicklookd[555] [QL] 'Creating thumbnail - cancelled' timed out for '<QLThumbnailRequest /Users/troylindstrom/Downloads/About Downloads.pdf>' (Start date: 2011-01-29 03:03:35 -0800)
    1/29/11 3:05:52 AM quicklookd[560] [QL] 'Creating thumbnail' timed out for '<QLThumbnailRequest /Users/troylindstrom/Downloads/About Downloads.pdf>' (Start date: 2011-01-29 03:05:32 -0800)
    1/29/11 3:06:44 AM quicklookd[563] [QL] 'Creating thumbnail' timed out for '<QLThumbnailRequest /Users/troylindstrom/Downloads/images-3.jpeg>' (Start date: 2011-01-29 03:06:22 -0800)
    1/29/11 6:37:03 AM com.apple.launchd.peruser.501[90] ([0x0-0x86086].com.apple.Preview[708]) Exited: Killed
    1/29/11 6:37:03 AM com.apple.launchd.peruser.501[90] ([0x0-0x8a08a].com.apple.systemevents[721]) Exited: Killed
    1/29/11 6:37:03 AM com.apple.launchd.peruser.501[90] (com.apple.AirPortBaseStationAgent[113]) Exited: Killed
    1/29/11 6:37:13 AM com.apple.launchd[1] * launchd[1] has started up. *
    1/29/11 6:37:42 AM com.apple.UserEventAgent-LoginWindow[81] ALF error: cannot find useragent 1102
    1/29/11 6:37:42 AM com.apple.UserEventAgent-LoginWindow[81] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/29/11 6:37:42 AM com.apple.launchd.peruser.501[89] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/29/11 6:37:50 AM com.apple.WindowServer[54] Sat Jan 29 06:37:50 Troy-Lindstroms-MacBook.local WindowServer[54] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/29/11 6:37:52 AM com.apple.launchd.peruser.501[89] (com.apple.Kerberos.renew.plist[109]) Exited with exit code: 1
    1/29/11 6:38:03 AM [0x0-0x8008].com.skype.skype[113] Main starting with pid 113 parent pid 89
    1/29/11 6:38:05 AM Skype[113] SkypeApplication::init called
    1/29/11 12:14:57 PM [0x0-0x36036].com.apple.CharacterPaletteIM[330] objc[330]: Class ThinDividerSplitView is implemented in both /System/Library/Input Methods/CharacterPalette.app/Contents/MacOS/CharacterPalette and /System/Library/Input Methods/CharacterPalette.app/Contents/PlugIns/RomanView.CharPalettePlugin/Conte nts/MacOS/RomanView. One of the two will be used. Which one is undefined.
    1/29/11 12:43:40 PM [0x0-0x39039].com.apple.CharacterPaletteIM[346] objc[346]: Class ThinDividerSplitView is implemented in both /System/Library/Input Methods/CharacterPalette.app/Contents/MacOS/CharacterPalette and /System/Library/Input Methods/CharacterPalette.app/Contents/PlugIns/RomanView.CharPalettePlugin/Conte nts/MacOS/RomanView. One of the two will be used. Which one is undefined.
    1/29/11 6:52:46 PM com.apple.launchd.peruser.501[89] ([0x0-0xf00f].com.apple.Safari[131]) Exited: Terminated
    1/29/11 6:52:59 PM com.apple.launchd.peruser.501[89] ([0x0-0x1e01e].com.apple.AddressBook[206]) Exited: Terminated
    1/29/11 6:52:59 PM loginwindow[29] * -[NSCFArray objectAtIndex:]: index (1) beyond bounds (1)
    1/29/11 6:52:59 PM com.apple.loginwindow[29] 2011-01-29 18:52:59.446 loginwindow[29:107] * -[NSCFArray objectAtIndex:]: index (1) beyond bounds (1)
    1/29/11 6:53:14 PM com.apple.launchd.peruser.501[89] (com.apple.AirPortBaseStationAgent[111]) Exited: Killed
    1/30/11 9:17:52 AM com.apple.launchd[1] * launchd[1] has started up. *
    1/30/11 9:19:51 AM com.apple.fontd[66] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/30/11 9:19:51 AM com.apple.WindowServer[68] Sun Jan 30 09:19:51 Troy-Lindstroms-MacBook.local WindowServer[68] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/30/11 9:19:54 AM com.apple.fontd[66] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/30/11 9:20:00 AM com.apple.UserEventAgent-LoginWindow[78] ALF error: cannot find useragent 1102
    1/30/11 9:20:00 AM com.apple.UserEventAgent-LoginWindow[78] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/30/11 9:20:00 AM com.apple.launchd.peruser.501[86] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/30/11 9:20:02 AM fontd[98] Database content version mismatch (stored(15) != expected(14))
    1/30/11 9:20:04 AM SoftwareUpdateCheck[94] Checking for updates
    1/30/11 9:20:05 AM storeagent[102] port created
    1/30/11 9:20:08 AM com.apple.launchd.peruser.501[86] (com.apple.Kerberos.renew.plist[109]) Exited with exit code: 1
    1/30/11 9:20:38 AM com.apple.launchd.peruser.501[86] (com.apple.AirPortBaseStationAgent[111]) Exited: Killed
    1/30/11 9:20:39 AM com.apple.loginwindow[22] shutdown: / is busy updating; waiting for lock
    1/30/11 9:20:44 AM com.apple.launchd[1] (com.apple.suhelperd[101]) Exited with exit code: 2
    1/30/11 9:20:45 AM com.apple.launchd.peruser.501[86] ([0x0-0x6006].SoftwareUpdateCheck[94]) Exited with exit code: 102
    1/30/11 9:20:49 AM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
    1/30/11 9:20:55 AM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
    1/30/11 9:21:16 AM com.apple.launchd[1] * launchd[1] has started up. *
    1/30/11 9:22:04 AM com.apple.UserEventAgent-LoginWindow[81] ALF error: cannot find useragent 1102
    1/30/11 9:22:04 AM com.apple.UserEventAgent-LoginWindow[81] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/30/11 9:22:04 AM com.apple.launchd.peruser.501[89] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/30/11 9:22:07 AM fontd[101] Database content version mismatch (stored(15) != expected(14))
    1/30/11 9:22:07 AM fontd[101] Failed to open read-only database, regenerating DB
    1/30/11 9:22:11 AM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/30/11 9:22:13 AM com.apple.launchd.peruser.501[89] (com.apple.Kerberos.renew.plist[111]) Exited with exit code: 1
    1/30/11 9:22:19 AM com.apple.WindowServer[69] Sun Jan 30 09:22:19 Troy-Lindstroms-MacBook.local WindowServer[69] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/30/11 9:22:26 AM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/30/11 9:22:26 AM [0x0-0x9009].com.skype.skype[116] Main starting with pid 116 parent pid 89
    1/30/11 9:22:28 AM Skype[116] SkypeApplication::init called
    1/30/11 10:33:53 AM com.apple.launchd.peruser.501[89] (com.apple.AirPortBaseStationAgent[113]) Exited: Killed
    1/30/11 10:34:02 AM com.apple.launchd[1] * launchd[1] has started up. *
    1/30/11 10:34:26 AM com.apple.launchd.peruser.501[86] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/30/11 10:34:26 AM com.apple.UserEventAgent-LoginWindow[79] ALF error: cannot find useragent 1102
    1/30/11 10:34:26 AM com.apple.UserEventAgent-LoginWindow[79] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/30/11 10:34:28 AM com.apple.launchd.peruser.501[86] (com.apple.Kerberos.renew.plist[107]) Exited with exit code: 1
    1/30/11 10:34:32 AM [0x0-0x8008].com.skype.skype[112] Main starting with pid 112 parent pid 86
    1/30/11 10:34:36 AM Skype[112] SkypeApplication::init called
    1/30/11 3:37:45 PM com.apple.launchd[1] * launchd[1] has started up. *
    1/30/11 3:50:19 PM com.apple.fontd[68] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/30/11 3:50:19 PM com.apple.WindowServer[69] Sun Jan 30 15:50:19 Troy-Lindstroms-MacBook.local WindowServer[69] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/30/11 3:50:21 PM com.apple.fontd[68] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/30/11 3:50:52 PM com.apple.coreservicesd[45] ThrottleProcessIO: throttling disk i/o
    1/30/11 3:53:14 PM com.apple.UserEventAgent-LoginWindow[80] ALF error: cannot find useragent 1102
    1/30/11 3:53:14 PM com.apple.UserEventAgent-LoginWindow[80] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/30/11 3:53:14 PM com.apple.launchd.peruser.501[90] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/30/11 3:53:15 PM fontd[101] Database content version mismatch (stored(15) != expected(14))
    1/30/11 3:53:18 PM com.apple.coreservicesd[45] ThrottleProcessIO: throttling disk i/o
    1/30/11 3:53:20 PM com.apple.launchd.peruser.501[90] (com.apple.Kerberos.renew.plist[109]) Exited with exit code: 1
    1/30/11 4:00:53 PM com.apple.launchd.peruser.501[90] (com.apple.AirPortBaseStationAgent[111]) Exited: Killed
    1/30/11 4:12:07 PM com.apple.launchd[1] * launchd[1] has started up. *
    1/30/11 4:12:56 PM com.apple.UserEventAgent-LoginWindow[81] ALF error: cannot find useragent 1102
    1/30/11 4:12:56 PM com.apple.UserEventAgent-LoginWindow[81] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/30/11 4:12:56 PM com.apple.launchd.peruser.501[89] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/30/11 4:12:59 PM fontd[101] Database content version mismatch (stored(15) != expected(14))
    1/30/11 4:12:59 PM fontd[101] Failed to open read-only database, regenerating DB
    1/30/11 4:13:06 PM com.apple.launchd.peruser.501[89] (com.apple.Kerberos.renew.plist[111]) Exited with exit code: 1
    1/30/11 4:13:15 PM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/30/11 4:13:21 PM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/30/11 4:13:21 PM [0x0-0x9009].com.skype.skype[116] Main starting with pid 116 parent pid 89
    1/30/11 4:13:23 PM Skype[116] SkypeApplication::init called
    1/30/11 5:12:33 PM com.apple.WindowServer[69] Sun Jan 30 17:12:33 Troy-Lindstroms-MacBook.local WindowServer[69] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/30/11 5:12:34 PM com.apple.RemoteUI[169] CoreAnimation: rendering error 501
    1/30/11 5:12:46 PM com.apple.launchd.peruser.501[89] ([0x0-0x9009].com.skype.skype[116]) Exited: Terminated
    1/30/11 5:12:49 PM com.apple.RemoteUI[169] HTTP2 Streaming Reads ON
    1/30/11 5:13:12 PM System Preferences[175] .scriptSuite warning for result type of command 'timedLoad' in suite 'SystemPreferences': the type NSNumber ('long') doesn't match the result Apple event code ('doub').
    1/31/11 12:17:59 AM com.apple.launchd[1] (com.apple.aslmanager) Throttling respawn: Will start in 5 seconds
    1/31/11 12:54:05 AM com.apple.launchd.peruser.501[89] ([0x0-0x18018].com.apple.Safari[180]) Exited: Terminated
    1/31/11 1:31:00 AM com.apple.launchd.peruser.501[89] (com.apple.AirPortBaseStationAgent[113]) Exited: Killed
    1/31/11 1:31:24 AM com.apple.launchd[1] * launchd[1] has started up. *
    1/31/11 1:33:28 AM com.apple.fontd[66] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/31/11 1:33:29 AM com.apple.WindowServer[67] Mon Jan 31 01:33:29 Troy-Lindstroms-MacBook.local WindowServer[67] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/31/11 1:33:31 AM com.apple.fontd[66] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/31/11 1:33:48 AM com.apple.UserEventAgent-LoginWindow[76] ALF error: cannot find useragent 1102
    1/31/11 1:33:48 AM com.apple.UserEventAgent-LoginWindow[76] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/31/11 1:33:48 AM com.apple.launchd.peruser.501[86] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/31/11 1:33:50 AM fontd[96] Database content version mismatch (stored(15) != expected(14))
    1/31/11 1:33:54 AM com.apple.launchd.peruser.501[86] (com.apple.Kerberos.renew.plist[105]) Exited with exit code: 1
    1/31/11 1:34:13 AM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
    1/31/11 1:34:13 AM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
    1/31/11 1:44:00 AM com.apple.launchd.peruser.501[86] (com.apple.AirPortBaseStationAgent[107]) Exited: Killed
    1/31/11 1:44:10 AM com.apple.launchd[1] * launchd[1] has started up. *
    1/31/11 1:44:43 AM com.apple.launchd.peruser.501[86] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    1/31/11 1:44:43 AM fontd[95] Database content version mismatch (stored(15) != expected(14))
    1/31/11 1:44:43 AM fontd[95] Failed to open read-only database, regenerating DB
    1/31/11 1:44:44 AM com.apple.UserEventAgent-LoginWindow[79] ALF error: cannot find useragent 1102
    1/31/11 1:44:44 AM com.apple.UserEventAgent-LoginWindow[79] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
    1/31/11 1:44:45 AM com.apple.launchd.peruser.501[86] (com.apple.Kerberos.renew.plist[108]) Exited with exit code: 1
    1/31/11 1:44:45 AM com.apple.fontd[95] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/31/11 1:44:57 AM com.apple.fontd[95] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
    1/31/11 1:44:58 AM [0x0-0x8008].com.skype.skype[112] Main starting with pid 112 parent pid 86
    1/31/11 1:45:00 AM Skype[112] SkypeApplication::init called
    1/31/11 2:00:28 AM com.apple.launchd[1] (com.apple.suhelperd[141]) Exited with exit code: 2
    Can anyone see the issue or tell me what I need to do to fix this thing???

    Which MacBook model? Did it come with OSX 10.6 or did you upgrade it?

  • Repair Disk Permissions - ACL Errors

    I opened Disk Utility and repaired disk permissions last night and was surprised to find six errors. I ran it again, and the first three errors disappeared. But the other three remain even after I repaired disk permissions two more times.
    These are the errors:
    ACL found but not expected on "Applications/Utilities".
    ACL found but not expected on "Applications".
    ACL found but not expected on "Library".
    Does anyone know what they mean, and how I can fix them?
    Thanks.

    Hi, they were common before the update to 10.5.2, and than they went away for the most part. There is much information on them with a search. Google the ACL errors and you will see what I mean. I hesitate to offer a solution because there's so many conflicting statements.
    Ray

Maybe you are looking for