Commit hook to find out who is holding a lock?

[Alban Hertroys]

Hi all,

We're having an issue where files in our single shared repository are 
being locked by 'something' and we're trying to figure out what is causing 
this. The lock conflict only seems to happen on commits or updates, most 
often on commits. Meanwhile the files are being used (read) by a server 
process (tscom3, part of WebFOCUS) on the machine hosting the repository.

Hence, I wonder whether it would be possible to add a debugging 
commit-hook that tells me what process is holding the lock if there is 
any?

The options are probably rather limited on Windows 7 (dev machines) or 
Windows 2008R2 (host machine). I know almost nothing about scripting or 
file lockingon this OS. Of course we have Python, but I haven't done 
anything file locking related and my Python-foo is rather rusty. Does 
something like that exist or does anyone have some pointers on how to get 
to this information? Much appreciated.

Regards,

Alban Hertroys.


alban.hertroys at apollovredestein.com
T: 




 	Apollo Vredestein B.V. - P.O. Box 27 - 7500 AA  Enschede - The Netherlands - 
Chamber of Commerce number 34223268 - http://www.apollovredestein.com	 

The information contained in this e-mail is intended solely for the use of the 
individual or entity to whom it is addressed and others authorized to receive 
it. You are hereby notified that any disclosure, copying, distribution or 
action in relation to the contents of this information is strictly prohibited. 
If you are not the intended recipient, please delete this message and any 
attachments and advise the sender by return e-mail. The confidentiality of this 
message is not warranted. Apollo Vredestein B.V. rules out any and every 
liability resulting from this or any other electronic transmission.