Re: remote cvs connection analasys (debug)

[Harry Putnam]

Harry Putnam <address@hidden> writes:

[...]

> I wondered if there is a way to force verbosity, where the negotiation
> get printed to tty or something similar so that I can see what is the
> problem.  The normal flags for that kind of stuff -[vV] are taken for
> other things and I see no `debug' or `verbose' option in man cvs
>
> A failed attempt looks like this:

>  $ cvs -d :pserver:address@hidden:/usr/local/cvsroot login
> Logging in to :pserver:address@hidden:2401/usr/local/cvsroot CVS
> password: <password> cvs [login aborted]: recv() from server
> cvs.gnus.org: Connection reset by peer

[...]

address@hidden (Larry Jones) writes:

> Harry Putnam writes:
 
>>  $ cvs -d :pserver:address@hidden:/usr/local/cvsroot login
>> Logging in to :pserver:address@hidden:2401/usr/local/cvsroot CVS
>> password: <password> cvs [login aborted]: recv() from server
>> cvs.gnus.org: Connection reset by peer

> Either the server is misconfigured or it's a buggy version of CVS.  If
> it doesn't work at all it's the former, if it just doesn't work for
> login it's the later.

Any one have a substantive suggestion here?
Some way to get more diagnostic output?

Larry's response only repeated the patently obvious.
And as I mentioned.  I'm able to connect to other cvs servers.
So a misconfiguration is a pretty good guess.  Question is, how to
determine what is misconfigured.  (From my end)