Linked by Thom Holwerda on Sun 8th Jan 2006 21:31 UTC
Mac OS X "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."
Thread beginning with comment 83428
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

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:
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.

Reply Parent Score: 1

jziegler Member since:

Well, on Linux (and I guess other Unixes as well), you _can_ delete a file that is in use.

The thing is, only the directory entry will be deleted. The inode and the file "behind" it will continue exists, until all handles to that inode are closed. At that moment, the file itself will disappear as well.

However, you are right about lsof. fuser might be even better, in some cases. I like it for checking TCP ports in use.

Reply Parent Score: 1