|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|
Your working copy of the sources can be on a different machine than the repository. Using CVS in this manner is known as client/server operation. You run CVS on a machine which can mount your working directory, known as the client, and tell it to communicate to a machine which can mount the repository, known as the server. Generally, using a remote repository is just like using a local one, except that the format of the repository name is:
Specifying a password in the repository name is not recommended during
checkout, since this will cause CVS to store a cleartext copy of the
password in each created directory.
cvs login first instead
(see section Using the client with password authentication).
The details of exactly what needs to be set up depend on how you are connecting to the server.
|2.9.1 Server requirements||Memory and other resources for servers|
|2.9.2 The connection method||Connection methods and method options|
|2.9.3 Connecting with rsh|| Using the |
|2.9.4 Direct connection with password authentication||Direct connections using passwords|
|2.9.5 Direct connection with GSSAPI||Direct connections using GSSAPI|
|2.9.6 Direct connection with Kerberos||Direct connections with Kerberos|
|2.9.7 Connecting with fork|| Using a forked |
|2.9.8 Distributing load across several CVS servers|
This document was generated on September, 14 2007 using texi2html 1.76.