from http://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/hiutil.1.html via https://discussions.apple.com/thread/3189362?start=0&tstart=0hiutil is for creating and examining .helpindex files. These files were historically created by Help Indexer.app, which now calls this tool.
I found the tool CleanMyMac is good to
- empty cache files
- remove logs
- securely erase files & trash can
- uninstaller that can completely uninstall applications
It also finds system junk and removes it.
It may not be an essential tool to have but once every few weeks I let it perform a full scan and it seems my mac runs more smoothly again. Of course this might be a placebo effect - but if so it's a pretty good one![]()
OS X does this:I found the tool CleanMyMac is good to
- empty cache files
- remove logs
- securely erase files & trash can...
I found the tool CleanMyMac is good
Emptying caches slows down your Mac. They do not need emptying, unless something has gone wrong.I found the tool CleanMyMac is good to
- empty cache files
The daily, weekly and monthly periodic tasks that OS X runs already handles this.- remove logs
Like the option in the Finder- securely erase files & trash can
Most apps are uninstalled by trashing the app. Those that require more complex installation usually have an uninstaller.- uninstaller that can completely uninstall applications
Ah. "System junk". That's like Space junk, right?It also finds system junk and removes it.
Many of them are. The fact that they may be reviewed and praised on a blog or on a website does not necessarily indicate that they are useful or necessary for your Mac. You don't need any third-party apps to keep your Mac running efficiently.are those just paid reviews to make money from people who don't know better?
It actually does. In quite a lot of cases it's the settings which are kept in a file that cause the problems, not the application itself. Removing the app does only that, it does not remove the settings (that 4kB file in your user library). When you removed an application permanently there also is no reason to keep the settings. Keeping settings is only meaningful when you are reinstalling the app. In all other cases it is better when it is removed. This is proper administration of a system: keeping things that are necessary, getting rid of anything that isn't. It prevents problems.Most apps are uninstalled by trashing the app. Those that require more complex installation usually have an uninstaller.
A 4Kb text file in your user Library from a deleted app is not going to hurt anything.
It actually does. In quite a lot of cases it's the settings which are kept in a file that cause the problems, not the application itself. Removing the app does only that, it does not remove the settings (that 4kB file in your user library). When you removed an application permanently there also is no reason to keep the settings. Keeping settings is only meaningful when you are reinstalling the app. In all other cases it is better when it is removed. This is proper administration of a system: keeping things that are necessary, getting rid of anything that isn't. It prevents problems.
I wish OS X had real application management. The MAS is one step in the right direction but it still lacks tremendously in the uninstalling department. I wish there was just 1 central application manager in OS X where you can uninstall apps. Windows has a major advantage over OS X in this area. It has that central application manager for uninstalling stuff. It also has uninstallers that give you the option to keep or delete the settings. Linux has everything except the option for deleting or keeping settings (you need to manually delete the settings just like in OS X).
Corrupted file, different version than what you are installing, wrong setting, incompatibility with the new OS (we've seen strange things with 10.4 -> 10.5), etc. There are many people who had to delete the plist for Finder, the firewall (consistently having to allow the app you already allowed permission), etc. to get things to work again. It happens to the in-built apps as well as ones from 3rd parties. Not something you'd run in regularly luckily but it can happen.How can a PLIST file of a deleted application muck with one's system?
I agree that many problems in OS X are caused by corrupt or wrong settings for the OS or existing apps, but we're talking about plists left over from DELETED applications.There are many people who had to delete the plist for Finder, etc. to get things to work again.
Doesn't matter, file will never be read.Corrupted file,
We're not installing the app. We've deleted it.different version than what you are installing,
Doesn't matter. App will never be launched to read the wrong setting: it's deleted.wrong setting
Again, file will never be read. Doesn't matter.incompatibility with the new OS
Get rid of it, it is JUNK (Sorry had to Capitalise this.)
If there are problems and only if, then the better tool is Onyx.
It actually doesn't. A plist from a deleted app has zero impact on a system, beyond taking up a few KB of drive space. It's no different that a simple text file. It is never read, since the only app that would have accessed it is no longer installed.It actually does.
It actually does. In quite a lot of cases it's the settings which are kept in a file that cause the problems, not the application itself. Removing the app does only that, it does not remove the settings (that 4kB file in your user library). When you removed an application permanently there also is no reason to keep the settings. Keeping settings is only meaningful when you are reinstalling the app. In all other cases it is better when it is removed. This is proper administration of a system: keeping things that are necessary, getting rid of anything that isn't. It prevents problems.
I wish OS X had real application management. The MAS is one step in the right direction but it still lacks tremendously in the uninstalling department. I wish there was just 1 central application manager in OS X where you can uninstall apps. Windows has a major advantage over OS X in this area. It has that central application manager for uninstalling stuff. It also has uninstallers that give you the option to keep or delete the settings. Linux has everything except the option for deleting or keeping settings (you need to manually delete the settings just like in OS X).
Corrupted file, different version than what you are installing, wrong setting, incompatibility with the new OS (we've seen strange things with 10.4 -> 10.5), etc. There are many people who had to delete the plist for Finder, the firewall (consistently having to allow the app you already allowed permission), etc. to get things to work again. It happens to the in-built apps as well as ones from 3rd parties. Not something you'd run in regularly luckily but it can happen.
That is an assumption you are making. There are many people who install an app in the future again. Say when you run a trial version and you need to install the full version because the app maker doesn't allow you to upgrade from the trial to the full. There are other use cases.Doesn't matter, file will never be read.
Exactly so why should we keep something that we are not going to use any more? Why delete the app in the first place as you can simply stop using it?We're not installing the app. We've deleted it.
Again, assumptions. There are use cases where this will happen.Doesn't matter. App will never be launched to read the wrong setting: it's deleted.
It actually does since people use 3rd party apps on their OS. The problem arises when you install a newer version later on or when you install a different app that might rely on certain software. There are many topics about this for nearly every mainstream OS regarding these kind of things. If you uninstall something because you want to not use it any more than everything it installed should be uninstalled. This prevents these kind of strange problems that are very hard to resolve.It actually doesn't. A plist from a deleted app has zero impact on a system, beyond taking up a few KB of drive space. It's no different that a simple text file. It is never read, since the only app that would have accessed it is no longer installed.
That is not a Windows problem, that is a problem with the uninstaller. A proper uninstaller simply uninstalls everything. There is no need to use the registry for example, it's just something that Windows offers for centralised configurations. It's not mandatory to use it.Windows sucks with this, you say everything gets uninstalled but this is by no means true, many times there are traces found in the registry and they interfere, not so on a mac if the App is deleted the plist file does nothing else then just occupying lets say 4 KB on your disk.
Which is exactly what happens with the crappy uninstallers in Windows. The problem here is again not the OS but the uninstaller itself.Left over launchDeamons/Agents can affect the System but they are rare, almost all Apps which install these have uninstallers.
The discussion is about deleted apps, not reinstalled apps. A plist left behind from a deleted app has no effect on anything, except consuming a tiny amount of drive space. If an app is reinstalled, that's a different scenario from the one you responded to, and in such cases, leaving a plist may be advantageous, as it may save the user from having to re-set app preferences. In the rare cases where a plist may be corrupted, it's usually detected while using the app, not on removal or reinstallation.It actually does since people use 3rd party apps on their OS. The problem arises when you install a newer version later on or when you install a different app that might rely on certain software. There are many topics about this for nearly every mainstream OS regarding these kind of things. If you uninstall something because you want to not use it any more than everything it installed should be uninstalled. This prevents these kind of strange problems that are very hard to resolve.
one .bom and one .plist file). Is it safe and advisable to remove those as well? I came across some warnings against removing them, as they might screw up permissions and permissions repair, but does it also apply to deleting references for uninstalled apps? Thank you.
Most evidence suggests that Disk Utility's Repair Permissions does NOT do ANYTHING for third-party installed software.But I would like to ask about the files in the private/var/db/receipts folder (usually one .bom and one .plist file). Is it safe and advisable to remove those as well? I came across some warnings against removing them, as they might screw up permissions and permissions repair,