[cvsnt] Re: Server cannot lock

Bo Berglund bo.berglund at telia.com
Thu May 19 20:48:07 BST 2005


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 Thu, 19 May 2005 13:57:28 -0500, "Paul Ardis"
<paul.ardis at gmail.com> wrote:

>Sorry, I should have listed the exact command earlier.  What I'm doing is 
>this:
>
>cvs -d :local:Z:\ -N commit -m "initial commit"
>
There you are, don't do this! :local: means that your own CPU is doing
all of the processing on the remote files across the network. CVS is
*very* I/O intensive and will need to create large numbers of files
during operations, files that are created, renamed and deleted in
rapid succession. Not very feasable across a network.

Instead as a test do this (replace the two names with proper data):
cvs -d :sspi:cvsserver_name:/repository_alias_name ls

This should display a list of the directories at the top of your
repository on the server. Typically in a repository with some stuff
inside (like my test server has) you will get a listing similar to
this:

E:\temp>cvs -d :sspi:ALTAIR:/PC ls
Listing modules on server

Advance
BosseTest
CVSMailer
CVSNT
CVSROOT
ImportTest251
ModuleAA
ModuleImp
ModuleImpx
ModuleXX
ModuleYY
ModuleZZ

E:\temp>

In your case you will probably only get the CVSROOT entry, but what
this does show you is that you have a working client/server connection
and you *do not* have to use the shared drive.
It will be much safer, faster and correct.


/Bo
(Bo Berglund, developer in Sweden)



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