[Top][All Lists]

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

RE: Installing CVS on Red Hat 7.0 -- Solution (xinetd.d)

From: Harnish, Joe
Subject: RE: Installing CVS on Red Hat 7.0 -- Solution (xinetd.d)
Date: Tue, 9 Oct 2001 11:43:47 -0400

After some very good suggestions, Larry Jones filled me in on the last little bit to get it working.  Here is the xinetd.d file that I am using (for others who may have this problem).

service cvspserver
        socket_type         = stream
        protocol            = tcp
        wait                = no
        user                = root
        server              = /usr/bin/cvs
        server_args         = -t -f --allow-root=/home/cvsroot pserver
        disable             = no
        passenv             = PATH

Thanks to all.


-----Original Message-----
From: address@hidden [mailto:address@hidden]
Sent: Monday, October 08, 2001 4:58 PM
To: address@hidden
Cc: address@hidden
Subject: Re: Installing CVS on Red Hat 7.0

Harnish, Joe writes:
> service cvspserver
> {
>         socket_type             = stream
>         protocol                = tcp
>         wait                    = no
>         user                    = root
>         server                  = /usr/bin/cvs
>         server_args             = cvs --allow-root=/home/cvsroot pserver
>         disable                 = no
> }

Is /usr/bin/cvs the correct path to CVS?

The server_args should not include "cvs", but should include "-t".
You may need to add "passenv = PATH".

> The line is in the /etc/services file for cvspserver to listen on 2401 tcp &
> udp.

CVS only uses TCP, so you don't need UDP.

> I have CVSROOT set in /etc/profile.  After I did that I created a
> blank file in /home/cvsroot/CVSROOT/ called passwd.  Then I added myself as
> a user into cvs (using the same password to login to the machine).  Next I
> ran:  kill -HUP pid.  Replacing pid with xinetd's pid number.  When I run a
> netstat -ta  --net | grep cvspserver I get nothing.  Is there anything
> special I need to do?  I think it is something really small that I am
> missing.

Check your syslog for error messages from xinetd.

-Larry Jones

These things just seem to happen. -- Calvin

reply via email to

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