[cvsnt] CVSNT :ext: BUG? (solved)

Guilherme Balena Versiani guibv at comunip.com.br
Thu Aug 14 18:37:28 BST 2008

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.

Hello CVSNT users,

I found the problem by inspecting root.cpp and server.cpp from the CVSNT 
source code.

For all of you with the same problem,

    just check if the /etc/cvsnt/PServer file is readable by the CVS users.

If not, then the errors like I described will occur.

NOTE: I think it would be a _very good idea_ to put this information to 
the CVSNT/Linux Install documentation, as most of people would like to 
protect CVSNT server configuration from being readable by anyone!!!...

Thank you,

Guilherme Balena Versiani.
ComunIP S/A

Guilherme Balena Versiani ha scritto:
> Tilo Riemer ha scritto:
>> At first you should check if it possible to connect to the server via 
>> ssh (without invoking cvs). For instance you can use putty to try to 
>> connect.
>> If this works you could use another CVS GUI. I recommend CrossVC XXL 
>> (http://www.crossvc.com). CrossVC supports access via ssh out of the box.
> I think you are going to the wrong side... I am sure I am able to 
> connect through ssh (in fact, I am able to connect to the server by 
> using TortoisePlink, putty, OpenSSH of Cygwin, OpenSSH from another 
> Linux machine, etc). I want to go two steps forward and say how you 
> could reproduce the problem.
> Let me make an introduction to the problem. When you use 
> :ext:user at domain:_path_to_repository_ in any cvs client (CVSNT, or any 
> other CVS taste), it works like below:
> 1) It takes CVS_RSH environment variable to connect to the server;
> 2) It spawns the command '$CVS_RSH -u user domain cvs server';
> 3) After authenticating and so forth (issued by the spawned process), 
> the client starts to talk with the server by using CVS default protocol 
> (pserver).
> If you observe the step 2 above, you will note that the CVS_RSH command 
> will issue 'cvs server' on the server machine. Just try it, and you will 
> see what I am saying.
> Then, if you just want to see the problem happen on CVSNT/Linux, just do 
> the following on the Linux CVSNT server machine (the same you installed 
> and configured the CVSNT, as I sent in my first e-mail):
>     $ cvsnt server
>     Root _path_to_repository_
>     E cvsnt [server aborted]: _path_to_repository_: no such repository
>     error
> What would be the right response? If you use the 'vanilla' CVS (not 
> CVSNT, like the version 1.12.12), then you will get the following:
>     $ cvs server
>     Root _path_to_repository_ << no response after this, the server will 
> wait next cmd
>     ls
>     M MyModuleA
>     M MyModuleB
>     M MyModuleC
>     M MyModuleD
>     M MyModuleE
>     M MyModuleF
>     ...
>     ok
> Did you get me now?
> Thank you,
> Guilherme Balena Versiani.
> ComunIP S/A
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
> 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