«

On Sat, Dec 5, 2009 at 23:17, W. eWatson <> wrote:
> J wrote:

>> And those are your only options, really. *From what I've been able to
>> see, there is no native ability in Linux to actually see who has a
>> lock on a file that's been opened. *And I completely understand your
>> frustration.

Crud.. that should have said no native ability in Windows... not Linux...

> Well, I'm pretty well done now. I fixed the program so it would write the
> file and close it. It did this successfully. I'll worry about getting the
> oddball file deleted later.

Cool. Glad you got it worked out... good luck!



--

Joan Crawford - "I, Joan Crawford, I believe in the dollar.
Everything I earn, I spend." -
http://www.brainyquote.com/quotes/au..._crawford.html

J wrote:

> But that being said, this brings to mind a question about this... in
> *nix, when I can't do something like delete a file or directory, or
> unmount a filesystem and cant find the cause, I can do an lsof and
> grep for references to the file/directory in question, then work from
> there to close anything that still has a lock.

It's been a while since a last had this problem. I found a program
named "handle.exe" somewhere on microsoft.com. It spits out a listing
showing which process has which files open. You can kill the offending
processes, and then you can delete your file.

I suppose Google can help you find this program.


Hope this helps,

-- HansM

Hans Mulder wrote:
> <div class="moz-text-flowed" style="font-family: -moz-fixed">J wrote:
>
>> But that being said, this brings to mind a question about this... in
>> *nix, when I can't do something like delete a file or directory, or
>> unmount a filesystem and cant find the cause, I can do an lsof and
>> grep for references to the file/directory in question, then work from
>> there to close anything that still has a lock.
>
> It's been a while since a last had this problem. I found a program
> named "handle.exe" somewhere on microsoft.com. It spits out a listing
> showing which process has which files open. You can kill the offending
> processes, and then you can delete your file.
>
> I suppose Google can help you find this program.
>
>
> Hope this helps,
>
> -- HansM
>
>
Handle.exe and "Process Explorer" (mentioned by J) are both from
Sysinternals, which was acquired by Microsoft, and to be found on their
site.

http://technet.microsoft.com/en-us/s...s/default.aspx

http://technet.microsoft.com/en-us/s.../bb896655.aspx for handle.exe
http://technet.microsoft.com/en-us/s.../bb896653.aspx for process explorer

But as long as I'm in the thread, I'll state that I suspect the problem to be simply that the OP is running his script inside some IDE, and it hasn't really ended. So the first thing I'd try is to exit the IDE, and see whether the file is then released.

DaveA