RE: problems accessing repository: no such repository (RESOLVED)

[Gabe Pinar]

> It might help to know exactly what you put in /etc/init.d/cvs.

service cvspserver
{
        enabled         = yes
        disable = no
        socket_type     = stream
        wait            = no
        user            = root
        server          = /usr/bin/cvs
        server_args     = -f --allow-root=/home/cvs pserver
}

> in the right place -- xinetd usually keeps its config files in
/etc/xinetd.d. 

I miswrote that in my original e-mail, the file is in /etc/xinetd.d/, sorry.

I am able to login now, thanks everyone.

--
 Gabe
-----Original Message-----
From: address@hidden [mailto:address@hidden
Sent: Thursday, September 05, 2002 9:33 PM
To: address@hidden
Cc: address@hidden
Subject: Re: problems accessing repository: no such repository


Gabe Pinar writes:
> 
> I added entries in /etc/services and made the correct entry for
> /etc/init.d/cvs.  Connections to port 2401 are working as advertised.

It might help to know exactly what you put in /etc/init.d/cvs.  You also
might want to check that you put it in the right place -- xinetd usually
keeps its config files in /etc/xinetd.d.

> I created a repository like this:
> cvs -d /home/cvs/CVSROOT init
>
> Set the environment variable:
> export CVSROOT=/home/cvs/CVSROOT
> cvs init

There's no need to do init twice -- it's generally best to set $CVSROOT
first and then just do "cvs init".  However, you almost certainly want
$CVSROOT to be just /home/cvs.

> I try to access the repository like this:
> cvs -d :pserver:address@hidden:/home/cvs/ login

Why the sudden switch from local mode to pserver mode?  In any event,
the path name there (/home/cvs/) must *exactly* match an --allow-root
argument in the pserver invocation in /etc/init.d/cvs.  And you don't
want the trailing slash -- it will confuse CVS sooner or later.

-Larry Jones

These things just seem to happen. -- Calvin