[cvsnt] CVSNT 2.0.6 fails in a batch file

John Peacock jpeacock at rowman.com
Tue Jul 22 20:10:33 BST 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.

Alexandre Augusto Drummond Barroso wrote:

> It seems CMD is spawning processes concurrently so the first process locks the file while the following processes fail.
> So you may use "start /w" before each command to make CMD wait the process termination before interpreting next command line.:

This *may* solve the problem, but then again it may not.  NTFS is very lazy 
about releasing filesystem locks (it's a "performance" hack) and it isn't too 
hard to create a race condition where supposedly atomic changes are blocked 
because the previous process' locks are not yet released.


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