[cvsnt] remote checkout fails to complete

Tony Hoyle tmh at nodomain.org
Fri Dec 6 19:21:43 GMT 2002

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 Fri, 6 Dec 2002 13:46:20 -0500, "Paul St. John"
<pstjohn at visible-bytes.com> wrote:

>> Set CVS_CLIENT_LOG on the client to the name of a file somewhere that
>> you can write to.  That'll produce <file>.out and <file>.in which
>> contains all the data.  It can get very large though.
>How do I do this with WinCvs client?  It doesn't seem to care about
>environment variables.

Just run it from the command line... the results should be identical.

>Can anyone expand on the comment that large binary files can
>cause cvs to slowdown and even stop?

If you are storing large binary files, each revision makes the
associated RCS file increase by the size of the binary file, which can
get very large.  cvsnt generally tries to put as much of an RCS file
as it can in memory.  With source code this isn't a problem - even
with many thousands of revisions the file is unlikely to get beyond
the capacity of the server.  However with large binaries these files
get very large very fast and will cause the server to slow down as it
breaks into swap.  On many Unix OSs they will terminate an application
that tries to eat that much memory very quickly, so the server

Processing binaries is also quite inefficient, and takes longer than
it should, largely for historical reasons.


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