[cvsnt] recovery from misfired commit

Anna Seg segfault at noao.edu
Fri Feb 14 00:24:36 GMT 2003

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


I am using the cvsnt latest and greatest for my cvs server, and wincvs 
on my clients.

I had a user add a binary file to the repository, and then try to commit 
it.  But, the file was open by another app causing a sharing violation 
and then the commit hung.  He canceled the commit by killing the process 
with the task manager.

Problem #1:  It left the lock files in the repository which denied 
access to the directory via the client.

My solution:  Deleted the lock files on the cvsnt server machine.

Problem #2:  After the lock files were deleted, I tried to commit the 
file again, and it *still* hung (I think the repository was confused).

My solution:  Deleted the file.ext,v in the repository, then used the 
wincvs client to re-add, then commit.  This seemed to work.

Is there a better way to do any of this?  I have a funny feeling that I 
am mis-managing my repository and I don't want to mess anything up.

Thanks for helping!


More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook