Hello, Jason Lim wrote:
Hi,
I also try this before and seem to be no luck for me.
Anyway, /etc/services already have this 2401 open.
In /etc/services there are only defined the associations between ports and names, but not "opened". Still, the port number must be defined in the /etc/xinetd/cvs, either with its name (defined in /etc/services) or with its number (when you don't wanna depend with /etc/services).
I'm believed this must be related to my port opening and cvs services was not start properly.
Is there anything related with the cvs xinetd service in the log files?
Thanks.
-----Original Message----- From: Alin Dobre [mailto:alin.dobre@ravantivirus.com] Sent: Wednesday, March 31, 2004 1:56 PM To: Jason Lim Subject: Re: [SLE] CVS connection refused
Hello,
You must set in your cvspserver xinetd configuration file: port = 2401 and then restart: /etc/init.d/xinetd restart
Regards, Alin.
Jason Lim wrote:
Hi,
Below is the configuration of my CVS
/etc/xinetd.d/cvs
service cvspserver
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = cvs
server = /usr/bin/cvs
server_args = -f --allow-root=/var/cvsroot pserver
}
Suse Linux 2.4.20-64GB-SMP #1 SMP Sat Feb 7 02:07:52 UTC 2004 i686 unknown unknown GNU/Linux
/var/cvsroot/CVSROOT/passwd (created by /usr/sbin/htpasswd)
myusername:KjsaTw4EW0MQM:cvs
export CVSROOT=:pserver:myusername@10.10.10.2:/var/cvsroot
export EDITOR=vi
-restart the server
-run command 'netstat -a |grep LISTEN' but cannot find any cvspserver or port 2401
- try with cvs login enter the password
myusername@tux:/var/cvsroot/CVSROOT> cvs login
(Logging in to myusername@10.10.10.2)
CVS password:
cvs [login aborted]: connect to 10.10.10.2:2401 failed: Connection refused
PLEASE HELP!
Thanks in advanced
- Jason Lim
-- Alin DOBRE Technical Support Engineer - RAV Division mailto:alin.dobre@ravantivirus.com Tel./Fax: +40-21-321.78.03 Hotline: +40-21-321.78.59; http://www.ravantivirus.com Worry less! RAV is watching. --------------------------- This message is confidential. It may also be privileged or otherwise protected by work product immunity or other legal rules. If you have received it by mistake please let us know by reply and then delete it from your system; you should not copy the message or disclose its contents to anyone.