What's Keeping Me? 1.0.5

Typo: "with it's advanced" --> "with its advanced"

I just find a simple rm -f of the file in the ~/.Trash/ path solves my issue nonetheless. What good is having a proper Unix system if we don't take advantage of that fact when the overlay interfaces choke at times.

Eric
http://www.codedevl.com

Too bad it still didn't work for me.

I'm still having problems with a folder that just won't go out of my Trash, no matter how hard I try.

Even sudo rm -rf inside ~/.Trashes failed!

And yes, I have tried restarting, logging out, holding Option, etc...

I wish it was not only trash specific. I never have this issue, but after I backup to my external using Super Duper, if i am running Bridge or PSCS3, I cannot eject my external, I wish i knew what was causing the issue more specifically than quitting to eject.

Damn, Cory. Gotta mention the function that actually applies to most people. I don't know anyone who's had issues emptying the trash in ages, but the disk-eject problem is an effing universal constant.

Thanks, Hank, for chiming in!

Great idea. Now can they make it so that it tells you what program is keeping an external hard drive from ejecting?

aka lsof|grep. at least this time we're not being charged for it....

Hi, I'm the author of the software. Just FYI: I understand where people say this app isn't necessary... and they're right if all it did was help you with emptying the trash when a file is in use. There's ways around that.

But the main function I designed this for was when you can't eject a disk because a file from the disk is busy. In that case it's very hard to identify which file is in use and which application is using that file.

So this application handles both situations which makes it more useful than just with the trash problem. Unfortunately TUAW didn't mention this capability... but I do appreciate their attention to my product!

I don't see why this is needed. Just do "secure empty trash."

This happens to me all the time, especially after deleting podcasts from iTunes. And really it shouldn't need third party software to solve. I consider this an OSX (minor) bug.