[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: help on cvspserver (in linux mandrake environnement)
From: |
Art |
Subject: |
RE: help on cvspserver (in linux mandrake environnement) |
Date: |
Thu, 17 Jan 2002 15:03:22 -0600 |
> -----Original Message-----
> From: address@hidden [mailto:address@hidden Behalf Of
> Matt Riechers
> Sent: Thursday, January 17, 2002 7:47 AM
> To: address@hidden
> Cc: address@hidden
...
> address@hidden wrote:
...
> > I don't manage to start the cvs pserver service on the linux
> server, though i
> > think the files /etc/inetd.conf and /etc/services are well
> configurate (whith
> > cvspserver on port 2401). I've buid a repository in a /usr/local/cvsroot
> > directory.
>
> The relavent contents of /etc/services and /etc/inetd.conf would
> help diagnose
> the problem.
I am also experiencing the same problem.
My system is 2.4.8-26mdk.
My services files includes:
cvspserver 2401/tcp cvspserver
cvspserver 2401/udp cvspserver
My system does not use inetd.conf, rather it uses:
xinetd.conf
xinetd.d/
and the dir has a file called "cvs" which I thought included the
right stuff for cvspserver:
service cvspserver
{
disable = yes
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/sbin/cvspserver
}
However, I get this error in response to my request:
cvs [update aborted]: connect to a260(192.168.0.2):2401 failed: Connection
refus
ed
The command is:
cvs -d :pserver:address@hidden:/cvs update -d -P
I created anoncvs via cvsadmin and the Unix adduser commands.
> > When i try to start the pserver manually (in /usr/sbin) i get
> the message "cvs
> > [pserver aborting] bad port auth start:"
If I try this, I get:
cvs [pserver aborted]: bad auth protocol start:
> cvs pserver is meant to be run from inetd. What messages do you
> get when run
> from inetd?
>
> -Matt
So, I edited the "xinetd.d/cvs" file to say:
disable = no
vs "yes", killed xinetd and restarted it.
Now, my remote pserver command works!
I wish I knew this was the right way to manage xinetd, or
that xinetd had a "restart" client command to direct it
to re-read its config files.
Well, at least I didn't have to reboot Linux!
Art