- iDefrag every few months if you have a spinning HD and create/delete a lot of files.
- Repair Disk Permissions when there is a OS point release (ie. 10.7.1, 10.7.2, ect.)
- And make sure the log folders don't get too large (OS X will normally keep the log files in check, but I've seen some users on this forum with 20+ GB worth of logs
)
Other than that OS X will maintain itself.
defrag is not needed and apple actually has a KB article stating that it can degrade performance.
No need to repair disk permissions any more. That was the case when osx was at the 10.1 level. now its more myth. There are times when it could be helpful but at this stage its not needed.
Log folders get archived by OSX's automated maintenance scripts.
This MacWorld article sums it up nicely on those points
No need to repair disk permissions any more. That was the case when osx was at the 10.1 level. now its more myth. There are times when it could be helpful but at this stage its not needed.
This MacWorld article sums it up nicely on those points
I didn't say it should never be run, but generally speaking its not necessary. By the same token, I've not repaired permissions in a couple of years and my machine is working as it was the first day - and I'm running LionI've installed Lion twice on two different iMacs, and both times Lion was buggy and glitchy until I repaired disk permissions. The other day I was having random bluetooth issues and repairing permissions fixed that too.
I only suggested iDefrag if you create and delete lots of files. And running it is not to defragment the files but to consolidate them and move the files back to the start of the disk platter (which is faster/has lower latency). Also iDefrag is aware of most of the tricks OS X uses to speed up disk access (Hot-Band, Metafile zone, ect.) and under normal circumstances will not decrease performance.
The permissions repair while not absolutely necessary, is more of a matinence thing to make sure installed updates match permissions listed in the package receipts. Remember ACL's exist mostly for security (protecting important files/folders) and having them set wrong can break this security model.
As for logs, I've personally never had OS X mis-manage the logs folder but I have seen at least 2 users with huge /private/var/log/ folders which is why I suggested keeping a eye on them. (Apple is not always smart about what they do. One of the updates on my 10.6.8 machine deleted my /System/Library/StartupItems/ folder)
.
defrag is not needed and apple actually has a KB article stating that it can degrade performance.
No need to repair disk permissions any more. That was the case when osx was at the 10.1 level. now its more myth. There are times when it could be helpful but at this stage its not needed.
This MacWorld article sums it up nicely on those points
Post hoc ergo propter hoc.Actually, doing a Permission Repair just saved my butt!!!
...
Smarter people than I may say Permission Repair is no longer necessary, but I just had first-hand experience to the contrary.
There are appropriate times to repair permissions. It just doesn't need to be done as routine maintenance. Some people repair, or recommend repairing permissions for situations where it isn't appropriate. Repairing permissions only addresses very specific issues. It is not a "cure all" or a general performance enhancer, and doesn't need to be done on a regular basis. It also doesn't address permissions problems with your files or 3rd party apps.Smarter people than I may say Permission Repair is no longer necessary, but I just had first-hand experience to the contrary.
Disk Utility repairs the permissions for files installed by the Mac OS X Installer, Software Update, or an Apple software installer. It doesnt repair permissions for your documents, your home folder, and third-party applications.
You can verify or repair permissions only on a disk with Mac OS X installed.
Does Disk Utility check permissions on all files?
Files that aren't installed as part of an Apple-originated installer package are not listed in a receipt and therefore are not checked. For example, if you install an application using a non-Apple installer application, or by copying it from a disk image, network volume, or other disk instead of installing it via Installer, a receipt file isn't created. This is expected. Some applications are designed to be installed in one of those ways.
Also, certain files whose permissions can be changed during normal usage without affecting their function are intentionally not checked.