This section concerns what to do if you are having trouble making a connection to a CVS server. If you are running the CVS command line client running on Windows, first upgrade the client to CVS 1.9.12 or later. The error reporting in earlier versions provided much less information about what the problem was. If the client is non-Windows, CVS 1.9 should be fine.
If the error messages are not sufficient to track down the problem, the next steps depend largely on which access method you are using.
cvs [pserver aborted]: bad auth protocol start: fooIf this fails to work, then make sure inetd is working right. Change the invocation in `inetd.conf' to run the echo program instead of cvs. For example:
2401 stream tcp nowait root /bin/echo echo helloAfter making that change and instructing inetd to re-read its configuration file, "telnet servername 2401" should show you the text hello and then the server should close the connection. If this doesn't work, you need to fix it before you can worry about CVS problems. On AIX systems, the system will often have its own program trying to use port 2401. This is AIX's problem in the sense that port 2401 is registered for use with CVS. I hear that there is an AIX patch available to address this problem. Another good debugging tool is the `-d' (debugging) option to inetd. Consult your system documentation for more information. If you seem to be connecting but get errors like:
cvs server: cannot open /root/.cvsignore: Permission denied cvs [server aborted]: can't chdir(/root): Permission deniedthen either you haven't specified `-f' in `inetd.conf' or your system is setting the
HOMEenvironment variable for programs being run by inetd. In the latter case, you can either have inetd run a shell script that unsets
HOMEand then runs CVS, or you can use
envto run CVS with a pristine environment.