[cvsnt] Re: cvs commit hangs when Visual SlickEdit views a file

Tony Hoyle tmh at nodomain.org
Mon Mar 24 14:00:15 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.


On 24 Mar 2003 14:07:08 +0100, Oliver Koltermann <okoltermann at gmx.de> wrote:


>But now for CVSNT: Isn't there a way of exiting cleanly in a situation
>like this? I have no good understanding of Win32 file i/o and don't
>know what kind of file open the VSlick editor uses. When looking at
>the CVSNT sources I think that every i/o error is catched and should
>produce an error. I don't understand how it can stop responding like
>it does.
>
>Do you have an idea of what happens?
>
It's likely that in certain circumstances an fopen() will wait until the file
is unlocked rather than produce an error.  I wouldn't expect it to wait
indefinately though.

cvs -t -t -t should give you a pretty good idea of where it's happening
normally, but if you've tried that and not found anything I'm a bit stumped.

Tony



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