> -----Original Message-----
> From: Thomas Wichmann [SMTP:[EMAIL PROTECTED]]
> Sent: Sunday, February 27, 2000 5:50 PM
> To:   [EMAIL PROTECTED]
> Subject:      CVS server problem on Solaris
> 
> 
> Moin, moin
> 
> I have a strange problem with "CVS 1.10  `Halibut' (client/server)".
> It is a not set CVSROOT variable problem on Solaris 7.
> 
> Everything seems to work fine except remote access from 
> a different nor the same machine using pserver.
> 
> In  /etc/inetd.conf  I have
> 
> cvspserver  stream  tcp  nowait  root  /usr/local/bin/cvs
> --allow-root=/data1/cvs pserver
        [smc]  Here is one problem.

        You need an extra "cvs" in there.  Remember, in /etc/inetd.conf, the
arguments to the
        command include argv[0], the name of the command...

        so:

        cvspserver stream tcp nowait root /usr/local/bin/cvs cvs
--allow-root=/data1/cvs pserver

        (all on one line, of course, in case my mailer breaks lines.)
        -- steve

> and in /etc/services 
> 
> cvspserver      2401/tcp                        # CVS authentification (by
> Wichmann)
> 
> In /data1/cvs/CVSROOT/passwd I have an account for "wichmann".
> 
> That is, what happens:
> 
> bash$ export CVSROOT=:pserver:wichmann@bpdev1-neu:/data1/cvs
> bash$ cvs login
> (Logging in to wichmann@bpdev1-neu)
> CVS password: 
> cvs [login aborted]: unrecognized auth response from bpdev1-neu: cvs
> pserver: No CVSROOT specified!  Please use the `-d' option
> 
        [smc]  Why the botched inetd.conf would give this sympton, 
        I don't konw...maybe there are other problems too.

> Ok and tried it different
> 
> 
> bash$ cvs -d :pserver:wichmann@bpdev1-neu:/data1/cvs login
> (Logging in to wichmann@bpdev1-neu)
> CVS password: 
> cvs [login aborted]: unrecognized auth response from bpdev1-neu: cvs
> pserver: No CVSROOT specified!  Please use the `-d' option
> 
> Looks like the error message is generated from the CVS server
> but how can I set a variable for the server part?
> 
> If I try to use CVS locally on the machine everything works as 
> expected. I have done a similar installation and setup on
> Debian 2.1 and have had no problems.
> 
> I don't understand this behavior.
> 
> Can someone help me out of this?
> 
> 
> Thomas

Reply via email to