[Cvsnt] Newbie, "No such repository" error on create repository

Bo Berglund bosse at agiusa.com
Thu Apr 4 19:06:42 BST 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.


See reply below at the bottom!

-----Original Message-----
From: Luke.W.Friendshuh at seagate.com
[mailto:Luke.W.Friendshuh at seagate.com]
Sent: den 4 april 2002 18:56
To: bo.berglund at telia.com
Subject: Re: [Cvsnt] Newbie, "No such repository" error on create
repository



We got it working!!

Yes!  I am so excited.....

Turns out the most helpful piece of information was on the "devguy" website
you pointed us to.

He had this section:



                CVSROOT

                Here are some sample CVSROOT values, which are either
assigned to the CVSROOT environment variable or follow the -d option on the
command line.

                Pserver, CVS server running on [UNI]+X:

                :pserver:username at tiger:/cvs

                SSH, CVS server running on [UNI]+X:

                :ext:username at tiger:/cvs

                For CVSNT with Windows NT/2000 clients (very secure):

==>                :ntserver:tiger:c:/cvs

                Pserver, CVSNT

                :pserver:username at tiger:c:/cvs
                :pserver:username at tiger:/c//cvs

                SSH, CVSNT

                :ext:username at tiger:c:/cvs
                :ext:username at tiger:/c//cvs



For the ntserver, you don't have a username@ as part of the CVSRoot.  That
was the main thing we were doing wrong from the client side.
The CVSRoot syntax that worked for us was:
     servername:/repository

(The ":" is important - if you don't have it in there, winCVS bombs with an
access to 0x0000 memory error.)

Our IT guy also reinstalled cvsnt using your instructions.

So between those two "fixes", everything seems to be working well.

Thank you very much!!!

- Luke.

PS.  is the "very secure" thing after the ntserver line sarcastic?
Most of the things I have read seem to say that the ntserver by itself is
not very secure.
That is why people go through the extra effort of having a pserver, right?

Reply:
ntserver *is* very secure because the communication (all of it) goes through
the
encrypted named pipe mechanism of Windows NT. The logon to the workstation
is
what is used as authentication and that controls the pipe too.
The reason people work with pserver is the following:
1) To enable access from Unix and Linux
2) Same for W95/98/ME because these platforms do not support named pipes

/Bo



_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs



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