[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

I had a hard time getting RH Linux 7.0 and pserver running.

From: mlham
Subject: I had a hard time getting RH Linux 7.0 and pserver running.
Date: Sun, 03 Dec 2000 06:09:27 -0000
User-agent: eGroups-EW/0.82

So here is what I learned after messing for a day to get the thing
running. Most of this is somewhere in the group, but I will try and
put it in one place :-)

One: use this list and PAY ATTENTION to the little details :-)

Two: you have to get xinetd from redhat. There is a patch and it seems
to work okay ... although I didn't test it for more than a few hours
so there may be other things broken in it know ;-)

Three: the "linux" bug that you can read about for the root issue etc.
means that the easiest way to get it to work is to use the variable
env in the cvspserver file (you have to make this yourself, it isn't
made for you by any of the rpms :-( so the one that is working on my
box is as follows:

cat /etc/xinetd.d/cvspserver 
# default: on
# description: The cvs system
service cvspserver
        socket_type     = stream
        wait            = no
        user            = root
        env             = HOME=/cvs
        server          = /usr/bin/cvs
        server_args     = -f --allow-root=/cvs pserver
        disable         = no
 I have my $CVSROOT set to /cvs ... that means that I made a directory
that is located there most people put it in either /opt/cvsroot or
/usr/local/cvsroot so don't be lead off track by that :-) Also DON'T
FORGET THE pserver part of the server_args ... I did, and it took me a
long time to figure out that it was the problem. Also, this is from a
totally vanilla install of RH 7.0, so you may get lucky and just cut
and paste it into a file called /etc/xinetd.d/cvspserver and then you
can go.

Four: You need to make sure that the services file has the cvspserver
ports listed in it that would be 2401 by default.

Five: you SHOULD make a group for cvs ... this is so that you can give
the people in the group the rights to the directory. I made one called
cvs. Using linuxconf seems to be the easiest way.

Six: you have to chown the $CVSROOT directory to be in the cvs group.
I did this as follows:
first, HACKED ... I made everyones default group on this server (this
box is totally standalone NFS or anything) to be the cvs group that I
made in item Five. Then I changed the /cvs by:
  chown root.cvs cvs from the / path
The reason for the HACK was I was frustrated ... I know that somewhere
there is the right way to make is so that cvs won't check in with the
user default group, but I couldn't remember where. If someone else can
remember what to do to make that happen perhaps you will share ... if
not I will add it in a later post :-)

Seven: chmod $CVSROOT with 775 so that the group has rights. This will
solve things like the history issue as well as other "problems". This
is however not all that secure, so keep that in mind.

Eight: restart the xinetd by running:
/etc/rc.d/init.d/xinetd restart as root.

Hope this helps anyone else trying to do this :-)


PS If I forgot something ... sorry ... I was just trying to help the
next person so please add it to the list so that it is easier for
everone. Also thanks very much to everyone that took the time to post
before this ... you all made my day :-}

reply via email to

[Prev in Thread] Current Thread [Next in Thread]