Re: remote cvs connection analasys (debug)

[Larry Jones]

Harry Putnam writes:
> 
> 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)

Let me spell it out more completely:  It's a server problem.  Either the
server is misconfigured, in which case *any* CVS operation will fail; or
the server is running a defective version of CVS, in which case only
login will fail.  If there are people who have directories checked out
from the server and they can still do things like update or log, then
you know that it's a defective version of CVS.  If there aren't any such
people that you can check with, try telnetting to the CVS server:

        telnet cvs.myhost.com 2401

If the connection is immediately closed, then the server is
misconfigured (most likely, the path to CVS is wrong in the
/etc/inted.conf file).  If the connection stays open, hit return and you
should get a "bad auth protocol start" error which indicates that the
server is a bad version (1.10.6 if memory serves).

More troubleshooting advice can be found in the manual:

        <http://www.cvshome.org/docs/manual/cvs_21.html#SEC182>

-Larry Jones

I thought my life would seem more interesting with a musical
score and a laugh track. -- Calvin