Unknown Report on Repair Disk Permissions?

I received the messages below when I repaired my disk permissions, not noticed these before, are there any to worry about?
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 "usr/sbin/pppd" has been modified and will not be repaired.
Warning: SUID file "usr/sbin/vpnd" has been modified and will not be repaired.
ACL found but not expected on "Applications/Utilities".
ACL found but not expected on "Applications".
ACL found but not expected on "Library".

these messages are harmless and should be ignored.
http://support.apple.com/kb/TS1448?viewlocale=en_US
everybody gets them.

Similar Messages

Repair Disk Permissions Error: The underlying task reported failure on exit

Hi All...
any idea about this error when trying to Repair Disk Permissions using "Disk Utility" :
"Error: The underlying task reported failure on exit."
No repair is made at all! It just stops right after being launched
It happens either when booting on the Leopard CD or on external FW drive...
Cheers guys!!

riccopicco wrote:
I've finally gave in, and bought an iMac.
Transferred my old G4 to the new, fesh, Leopard installed iMac Intel chip....
I've been getting the same thing just after 1 week with this new system!!!
Someone help!!!
It sounds as if you transferred the errors when you migrated your files from the G4. Something in that old filestructure that is not right. It might be the ownership of a single file somewhere.
Have you considered DiskWarrior?

Disk Utility & Repair Disk Permissions & Unknown User on External Seagate

I have a new iMac running Leopard and don't do stupid things to my mac. I have a couple external Seagate Freeagent drives but 1 of them is giving me a little trouble. So I figure, I'll try to repair disk permissions on it but the problem is when I go into Disk Utility, the Repair Disk Permissions option is NOT available. It's there, I just can't select it; it's grayed out. Why? I'm an admin! The other externals have this option available but not this one, so I'm not really sure what to do. I've about 300gb of family movies on it that I'd rather not wipe out just to be able to do a disk permission repair.
Whenever I do a command+i on the drive I do see an UNKNOWN user but this article, http://www.pcworld.com/article/145425-1/quickand_easy_folder_sharing_in105.html, leads me to believe that Apple hasn't done jack squat to allow us to fix the problem.
Thoughts? Suggestions? Thanks in advance!

mrpeepers wrote:
I don't think that statement is true.
I have 3 externals and can repair disk permission on all but 2. All my externals are for storage purposes and non have OSX installed, so that fact that I can repair disk permissions on them sort of contradicts what you say, however, the effectiveness of running a repair disk permission on a drive that doesn't have OSX may be nothing.
I don't know how you manage to repair permissions on externals without system files on them but what I said is quite true. Repair permissions ONLY checks permissions of system files against the database of correct permissions. It wouldn't know what to do with any other files and never touches them. It should also not be possible on non OS X drives. I've never seen it enabled on any of my external or secondary drives. I really wonder why and how it was enabled on your external drives.
I did have Tiger installed for 3 months before I got Leopard, but my externals have known nothing but Leopard.
That doesn't matter. the ownership of files on your external were set in Tiger and it remains in leopard. that's what causes the "unknown" user to show up.
The problem I'm having with one of the drives is that starting yesterday it's having difficulties mounting. Sometimes I restart the computer and the drive doesn't show. So in order to get it to show, I have to power down the external (which is and appears to be running) and then power it back up, and if that doesn't work, usually reseating the USB works.
Then again... My problems started happening after I installed CandyBar and applied some folder changes. I have since dumped it.
whatever problems you have with that external they have absolutely nothing to do with Candy bar. all candy bar does is change a few icon files on your main hard drive. that can have no effect on mountability of anything.
This sounds to me like a hardware problem with your external. the drive could be failing. the USB bus could be failing either on the drive or on the computer. One thing you could do is check to see if there are any firmware upgrades for that drive. Look at the manufacturer's website. also try testing the drive with another computer if you can.
On another note... Anyone use CandyBar and NOT have any problems or really like it? Maybe it was just a coincidence.
yes, I use it and REALLY like it. no problems whatsoever.

Repair Disk Permissions Report

I ran the Disk Utility, Repair Disk Permissions this morning and it came up with this. Is this something to be concerned about and if so how can it be fixed?
Repairing permissions for “Macintosh HD”
Permissions differ on "usr/share/derby", should be drwxr-xr-x , they are lrwxr-xr-x .
Repaired "usr/share/derby".
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
Permissions repair complete

Is this something to be concerned about
No. Click here for more information.
(50837)

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

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.

Odd errors in repairing disk permissions...

I get the following log when I go to repair my disk permissions:
Repairing permissions for “Mac”
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.
Anyone know what exactly this might mean?
Thanks in advance,
-J

Mac OS X 10.5: Disk Utility's Repair Disk Permissions reports issues with SUID files
http://docs.info.apple.com/article.html?artnum=306925
Quoted from above:
"You can safely ignore these messages. They are accurate but not a cause for concern."

Verifying/Repairing Disk Permissions

I have read in the Forum that one should run Disk Permissions before and after updates, and it doesn't hurt to run it once in a while anyway. But it isn't clear to me when one should verify and when one should repair. After verification, we get the message "Permissions verification complete. Privileges have been verified OR REPAIRED" (capitalization mine). If the verification takes care of repairs, when should one click on the "Repair Disk Permissions"? Thanks.

There's no point in verifying. Always repair. However, repairing permissions need only be done before installing new system updates or after installing third-party software that uses a proprietary installer.
Before installing system updates I recommend doing this:
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger, and 4.1 for Leopard) and/or TechTool Pro (4.6.1 for Leopard) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

Unix command to repair disk permissions

ARD 3.2.1
Send UNIX command>Template>Miscellaneous>Repair Disk Permissions
This command works but the report does not show the results under the correct computer. If several computers are given the command, they report back under the next computer name in the list even though they show correctly in the display under "Active Tasks".
Ron Taylor

Send
diskutil repairPermissions /
as the user "root" (no quotes).

When I repair disk permissions using Disk Utility and it says it's completed the task, I click on it again and it repairs more. This has been going on for hours now. Could there be that many wrong permissions? Should it get to "all repaired" eventually?

When I repair disk permissions using Disk Utility and it says it's completed the task, I click on it again and it repairs more. This has been going on for hours now. Could there be that many wrong permissions? Should it get to "all repaired" eventually?

It's normal behavior. You don't have to worry about. Most of what's listed is just a report of what the utility finds., not necessarily that there is omething wrong.
If you want to find out more, read the link below, or see the More Like This links on this page.
http://support.apple.com/kb/TS1448?viewlocale=en_US

Can't repair disk permissions or run Mac Software update application

I tried repairing the disk permissions and received the following error message:
Error: The underlying task reported failure on exit
Got the same error message when verifying the disk permissions. The verify disk option also failed.
Whenever I run this application to check for updates, it just bounces in the dock and disappears. Then I get this error box that says "The application Software Update quit unexpectedly". It then gives me 3 options to "ignore, report, and relaunch".
Any ideas would be appreciated.

Thanks for the fast reply. I was able to run the disk utility using the disk. But I got the same errors when I booted back up and tried to run the "repair disk permissions". Plus the "Software Update" program still crashed.

When run repair disk permissions?

I am going to upgrade from Snow Leopard to Mountain Lion.
I have heard/read that you're supposed to run repair disk permissions beforehand.
1. Should I run repair disk permissions on my brand new backup disk (am planning to backup Snow Leopard and all apps and docs before upgrading to Mountain Lion - - so can restore Snow Leopard etc. if want/need to)? If so, do I run repair disk permissions on the new backup disk before or after I partition the backup disk [am planning to have two sections, one with all the Snow Leopard stuff, and one for iMac backups that will be made after have upgraded to Mountain Lion])
2. When's the best time to run repair disk permissions on my iMac - - before I download Mountain Lion or right before I do the installation of Mountain Lion?
Thanks.

It's not a requirement, but it may help especially if you don't attend to the state of your running OS. I recommend doing this:
Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
Then you can proceed to click on the Install button after the upgrade finishes downloading. I also suggest you make a bootable backup of your current Snow Leopard system on an external drive just in case things go badly.

HT1452 Should I repair disk permissions?

"Permissions differ" came up about 50 times after verifying disk permissions. Should I repair disk permissions?

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 onwards:
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 onwards 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

Unknown Report on Repair Disk Permissions?

Similar Messages

Maybe you are looking for