[Top][All Lists]

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

CVS Manual -- additional Remote Server info for xinetd

From: Joe Larson
Subject: CVS Manual -- additional Remote Server info for xinetd
Date: Thu, 14 Feb 2002 15:38:51 -0600

Newer versions of Linux (and possibly other UNIX systems) prefer to use
xinetd instead of inetd.  Configuration of xinetd is somewhat different than
inetd.  I'm going to provide the configuration info I used to get cvs working
in pserver mode.  This information could be merged into the docs for
remote server setup using pserver.  On my machine, it replaces the setup
when using inetd.

First, you probably have a file called /etc/xinetd.conf.  On my system, this
file is very brief but includes this line:

includedir    /etc/xinetd.d

This means that all the files in the directory /etc/xinetd.d are also included.

I then CD'd to /etc/xinetd.d and copied the simplest file I found in there
happened to be for "finger").  The new file name should be called cvspserver.
I edited the file to read as follows:

# default: on
# description: CVS pserver
service cvspserver
        socket_type     = stream
        wait            = no
        user            = root
        server          = /usr/local/cvsroot/runcvs.sh

The runcvs.sh file is very simple:

/usr/bin/cvs -f --allow-root=/usr/local/cvsroot pserver 2>&1

I did it this way simply for testing purposes.  My runcvs.sh script had some
info in it for a while.  You could probably use server and server_args in the
file.  See the man pages for xinetd.

The next thing I did was to make sure that cvspserver existed in /etc/services:

cvspserver      2401/tcp                        # CVS client/server operations
cvspserver      2401/udp                        # CVS client/server operations

(These already existed on my machine.)

Tell xinetd to reload config.  He was running as process 552.

# kill -s USR2 552

Once this was completed, I just resolved some UNIX security issues and
ran just peachy.

-Joe Larson

reply via email to

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