[Top][All Lists]

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

Re: cvs login failure

From: luke
Subject: Re: cvs login failure
Date: Wed, 18 Oct 2000 14:55:03 +1100 (EST)

On 17 Oct, Derek R. Price wrote:

> > No, that's exactly what I used; it's the output from a script wrapped
> > around it that only starts an ssh connection to the cvs server machine
> > if there isn't already one running, and also sets some environment
> > variables.
>  That sure looks like the standard error message.  Are you sure you are 
> sending the
>  right user name?

>From the "(Logging in to address@hidden)" message, it seems so.

>  You said you move the CVS repository.

Yes; we moved it from /home/handy/cvs-archive to
/home/mantovani/cvs-archive.  We set up amd to export /home/mantovani
and also to make a synonymous entry called /home/handy (since handy is
now defunct), as a convenience.  We tried both, incidentally, in the
inetd.conf file (killing inetd appropriately), but that made no

>  Are you sure your ssh is
>  still forwarding the connection to the correct machine and not to another 
> without your
>  name in the password file?

Absolutely.  We use NIS for passwords.  They're only kept on one
machine.  And yes, the ssh forwards are always to localhost, so neither
the machine name at the client nor the server has to be hard-coded as
it were.

>  Are you sure the repository root (--allow-root=...) hasn't
>  changed and is it still being specified correctly to the pserver command?


cvspserver stream tcp nowait root /usr/sbin/tcpd /usr/bin/cvs 
--allow-root=/home/handy/cvs-archive pserver

>  Play with CVS_CLIENT_LOG and see if you can trace more of the authentication.

Ah!  This is what I was asking about and hoping for.  Some way to get
some extra logging or debug info.  I assume that the client defines
this env variable to be a filename, and log info is written to it.

I'll give that a try right now.  Thanks.


reply via email to

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