Constantly repairing disk permissions for Spotlight to work

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

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

Similar Messages

Worried about need to constantly repair disk permissions

Here is my analysis and conclusions as to why I need to constantly repair disk permissions:
I recently got the top-o'-the-line iMac (see info below) which shipped with Lion but since I wanted Snow Leopard (just because I have a few PowerPC games that I can't live without) I reformatted the hard drive - into 1 partition from the 2 that Lion had - and installed Snow Leopard and went back to business as usual....only with one **** great and fast computer. BTW, as far as I know this computer is exactly the same computer that shipped with Snow Leopard prior to Lion's introduction. I swore that I would never get another desktop computer because this one would last me forever. My only hesitation now is because the need to constantly repair permissions means something is not right. On the one hand I could just keep on repairing (daily?) the permissions for the next 20 years, or.... what? Is it possible (or should I be asking Apple itself instead of in this forum) that there is some other difference between the Snow Leopard and the Lion versions of this iMac - is this what "firmware" is all about? - that produces this constant need to repair permissions? If that's the case, would Apple give me a Snow Leopard-friendly logic board (and/or install the correct firmware) in exchange for the Lion logic board - or am I just going to have to live with having to perform this permissions-update function? Or is having to repair disk permissions not a big deal or something worrying about? Any ideas would be appreciated - thanks!
Hardware Overview:
Model Name:          iMac
Model Identifier:          iMac12,2
Processor Name:          Intel Core i7
Processor Speed:          3.4 GHz
Number Of Processors:          1
Total Number Of Cores:          4
L2 Cache (per core):          256 KB
L3 Cache:          8 MB
Memory:          12 GB
Boot ROM Version:          IM121.0047.B0A
SMC Version (system):          1.72f2
Hardware UUID:          B9D5A82D-6205-5FDD-BE77-46CC72811374

You do not need to repair permissions unless there's a specific problem.
For your info;
http://support.apple.com/kb/TS1448

Repair disk permissions for an external RAID drive?

Hello,
We are able to repair disk permissions on the hard drive, but can it be done on an external SCCI RAID drive? Is there software that is recommended that will repair and fix issues such as if the RAID drive was improperly removed without ejecting the drive? Or is that not needed?
Thanks,
Jordan

DiskWarrior repairs your directory, throws in some limited optimization (iPhoto's open in half the time is about all really), so if your "directory is out of order" it's not that big a deal really.
It's good to have on the shelf if you have a lot of Mac's, but ever since Tiger rolled around it seemed a lot of directory problems have disappeared on single user machines. It's pretty expensive for it's limited options.
With a RAID O (stripe) setup you should Disk Utility Erase w/Zero before setting up the RAID and laying data down. (in fact this is wise for all new drives at least once)
RAID O's should always be cloned (in the case of a boot RAID O) or backed up quite often because if one drive goes the whole set with data is lost.
Mirroring (RAID 1) is only necessary for extremely valuable one time data captures where a hard drive failure would be awlful. It doesn't make a good backup because any corruption, mistakes etc get immediatly written to the second drive.
Using automated cloning and backup software is better like (search Apple) DeJaVu. Auto clone the whole boot drive once a week and auto backup certain folders of files nightly.
Since cloning I haven't really too much need for drive maintainance software, if my RAID goes down for a data reason, (hasn't yet in 2 years of 24/7 operation) I simply option boot off the clone and repair/recover/reverse clone. I'm done in a hour, I even go out to eat or something while it's reverse cloning.
A good piece of software to have is (search Apple) OnyX, it's automation section will do a lot of cleanup and fixing certain things. Good to run it about once a month.
To find out more about cloning, visit Carbon Copy Cloner forums, they have donationware software too.

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

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

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

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

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

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?

Superdrive replacement not working? Try "repair disk permissions"

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

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

"Repair disk permissions" fixed install problem for me.

First time trying to install SL I got nothing. No windows opened, no error messages, no nothing. The system just looked at me like I was stupid.
After a good nights sleep I ran "repair disk permissions." It repaired a bunch of files (how did THAT happen???) and ran installer for SL again.
Worked perfectly!!! Gained a whopping 19.945 gig of HD space. YIKES!!!

First time trying to install SL I got nothing. No windows opened, no error messages, no nothing. The system just looked at me like I was stupid.
After a good nights sleep I ran "repair disk permissions." It repaired a bunch of files (how did THAT happen???) and ran installer for SL again.
Worked perfectly!!! Gained a whopping 19.945 gig of HD space. YIKES!!!

Repairing Disk Permissions - Not Working with Lion

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

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

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?

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

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

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

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

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

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

Working while repairing disk permissions?

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

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

Rationale for Repairing Disk Permissions

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

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

Constantly repairing disk permissions for Spotlight to work

Similar Messages

Maybe you are looking for