(Really, MacUpdate, why bother keeping it here at all?) -SB That original, now long defunct, 'iTrash' still shows up in MacUpdate's search with a disclaimer saying it is no longer supported by its developer. That vendor was 'Circus Ponies,' which I Googled, and which went out of business in 2016 after 13 years in operation. I just wonder if the developer was threatened with legal action for using the 'iTrash' name, which evidently was used for a now long-gone and unsupported app by a different vendor. Oddly enough, there is still nothing in Remove-It's description that mentions that is iTrash renamed. MacUpdate seems to have grafted the older reviews of iTrash onto Remove-It, which makes sense for the sake of continuity, and perhaps I left my review before that process was complete. (Which took me a while to figure out on my own.) Other reviewers (see MichaelHaeusler) had already made this clear. Otherwise I wouldn't have bothered to note that Remove-It was the successor app to iTrash. This is kind of strange, but I'm almost positive that when I left my review on 1/24/21 (below) there were no other reviews posted.

That's the kind of knowledge that Remove-It should ideally *not* require its users to have. That will require that you know a bit about how apps work under-the-covers. My advice: Either look elsewhere, or be very cautious using Remove-It-inspect its file removal list very carefully. It removed the app and several of its components, but it failed to identify the offending component as belonging to the app.

Just today, I used it to remove an app that installs components that cause Apple's osascript scripting engine to fail. And it has been leaving behind material that should be deleted. In the last year or so, it has been finding increasingly many app components to delete that should *not* be deleted (because they actually belong to another app, or a newer version of the deleted app). It does not 'package' its deleted content in the way AppDelete did (which made it easy to reverse a removal when necessary). However, I've grown increasingly unhappy with Remove-It. It has a similar interface and methodology. I moved to Remove-It from AppDelete, which always worked well but unfortunately was abandoned.

Localized: English, Dutch, Polish, German, Spanish, Portuguese, Italian, Slovak, Turkish, Persian, and French.

Protect related applications files (.plist, application support.

Protect custom applications and folders.

Application lister: shows all installed applications on all volumes (not just the Applications Folder).

Expert mode: To find even more possible related files.

Drop something into the trash and iTrash pops up. Deleting an application itself is mostly not enough and will leave several files untouched. In fact, I don't think you actually need to set the Mapall user/group, as long as the files are owned by crashPlan:backup.ĭo you have any directory services configured? I'm wondering if you are getting your crashPlan user or backup group from a directory service instead of the local one.Remove-It is an uninstall utility that uses a special search algorithm (Levenshtein Distance algorithm) to find all related files and deletes them when asked.Īpplications distribute several files throughout your system storage devices. You shouldn't need to concern yourself with the NFS options to make this work. Do a 'cat /etc/group | grep 1001' and see what you get. However, that would be odd at first glace, because usually a user's primary group is the same as their name (though it can be configured otherwise), which makes me curious if you have two groups on each system with a GID of 1001. You also showed that the GID of the group 'backup' (on each system) had a GID of 1001. What you showed in the first post was that the 'crashPlan' users (on each system) had a UID of 1001, and their primary group was the group with GID 1001, whatever that group happened to be. Each UID must be unique, and each GID must be unique.

First off, each user has a UID, and each group has a GID.

Download the new version TrashMe