Drive Mounty 4+

Great, but buggy

I bought this and have loved it for what it can do. I have a NAS that hosts all my media, but I set that system to shutdown every night to save power, and then automatically start up in the mornings. This app does a good job of remounting those drives in the morning when the NAS is available again, so bravo. HOWEVER, I too have found that when left running for several days at a time in the backround it will tend to stall, eat up all the RAM on the system and even create HUGE .plist files. I routinely have to go to it's preference folder and clear out tons of 1.22GB files or it will overrun my hard drive in a week or two. This has to be some weird bug that needs fixed. I have this setup on a remote mac mini that I only access via screen sharing, so once every couple weeks I'll remote into it to find Mac OS saying all my RAM is used and space on the HD is also low. I shutdown Drive Mounty, delete about 100GB worth of temp plist files it created and then restart. I actually still use this app daily even with these bugs because the service it provides is invaluable to me.

Frustrated

Drive Mounty worked as expected until I tried to purchase the Pro version. After going through the purchase process it froze on purchasing. When I try to restore purchase it freezes on "Contacting App Store". I've verifed that the purchase is in my history but it can't seem to complete or restore purchases.

Developer Response ,

Hi Us7300, sorry to hear this. I’ve just pushed up a fix for this issue. Please let me know if this solves the issue once released by Apple. Thx.

In need of an update

The one Pro is that it does what it's supposed to do. Most of the time.

There are five major Cons:
1) The applicaiton will consume all of your available memory if left running long enough.

2) Every 20 seconds it checks to see if the drives are mounted, and then writes a very verbose log entry into ~/Library/Containers/com.garrywhitten.drivemounty/Data/Library/Preferences/com.garrywhitten.drivemounty.plist, which means the file will get GINORMOUS. As a workaround I quit the app, go in to the file, and clear out the log section every few days.

3) Not a universal app, so no native M1 love.

4) The interface is a bit awkward and could use a re-work.

5) Hasn't been updated in over 2 years. I am assuming it has been abandonded by the developer at this point.

Overall it is a sub-par implementation for an app that serves such a simple purpose.