Larry Jones wrote:
For authentication, the 'cvs login' works if I login as a local user,
but If I use LDAP account, the login fails and gives the following
error.
cvs [login aborted]: connect to 192.168.2.5(192.168.2.5):2401 failed:
Connection refused
You've misdiagnosed the
Hi Larry,
I was able to rectify the Connection refused problem.
But I am getting the below problem.
$ export CVSROOT=:pserver:ksraghu@cvs-test:/proj1/cvs/repos/cvstest
$ cvs login
(Logging in to ksraghu@cvs-test)
CVS password:
cvs login: authorization failed: server cvs-test rejected access
Tom Plunket writes:
Or, since it apparently works as a local user, the server is
running but the ports are blocked or something. That all depends
on your platform, but places to start are /etc/hosts.allow,
/etc/hosts.deny and any firewalling software you might have set
up (such as
Raghavendra Kothamangala writes:
Is there any problem with CVS using LDAP server for authentication. Do
i have to setup anything else.
CVS just uses the standard getpwnam() (and getpwuid()) library routines
to get password information. As long as those routines know about LDAP,
CVS should
Hi,
I am running CVS on a Linux Redhat 7.1 box. I am using xinetd to
offer the cvspserver service. We have disabled telnet access to the
users on this machine.
For user information and passwords, this machine connects to an
external LDAP server.
For authentication, the 'cvs login' works if I
raghu_at_work writes:
For authentication, the 'cvs login' works if I login as a local user,
but If I use LDAP account, the login fails and gives the following
error.
cvs [login aborted]: connect to 192.168.2.5(192.168.2.5):2401 failed:
Connection refused
You've misdiagnosed the
