"Familiarity breeds contempt, right? So it stands to reason that anyone who uses a product extensively can find fault with it. I'm no exception - my work requires me to use Mac OS X every day, all day long, and although I am generally thrilled with its capabilities and reliability, some things about it really drive me up the wall."
To read all comments associated with this story, please click here.
Member since:2005-07-06
there should be a way to find out what process is making a file "busy" (Windows has major problems with that too.)
On Windows you can use this tool:
http://ccollomb.free.fr/unlocker/
It will tell you which process is using a particular file, and let you kill the file handle or the whole process.
Member since:2006-01-09
there should be a way to find out what process is making a file "busy" (Windows has major problems with that too.)
On Windows you can use this tool:
http://ccollomb.free.fr/unlocker/
It will tell you which process is using a particular file, and let you kill the file handle or the whole process.
On Linux, you can use lsof to get the PID of the offending application and then kill it so that you can release the resource being held by it.
Member since:
2005-07-07
insist on trying to make reasonable replies to an article that must have been meant as a joke.
I recall an urban myth story about a Tech support guy who got fired for:
"You need to collect all the pieces and paperwork that came with your computer, box it up, and return it to the store."
"Oh no! You mean...?"
"I'm afraid so. You're just too stupid to own a computer."
Actually, he does have some legitimate points hidden in that proposterously anal complaint list: there should be a way to find out what process is making a file "busy" (Windows has major problems with that too.) Permission errors and the spinning beachball hang, while both have gotten steadily better, are bugs that need to be fixed.