This is a complete list of all environment variables that affect CVS.
updatewill try hard to make the files in your working directory read-only. When this is not set, the default behavior is to permit modification of your working files.
$CVSROOTis not set, or if you wish to override it for one invocation, you can supply it on the command line: `cvs -d cvsroot cvs_command...' Once you have checked out a working directory, CVS stores the appropriate root (in the file `CVS/Root'), so normally you only need to worry about this when initially checking out a working directory.
$EDITOR. See section Committing your changes.
$RCSBINis not set, and no path is compiled into CVS, it will use
$PATHto try to find all programs it uses.
HOME. On Windows NT, the system will set
HOMEDRIVE, for example to `d:' and
HOMEPATH, for example to `\joe'. On Windows 95, you'll probably need to set
:ext:access method is specified. see section Connecting with rsh.
cvs. see section Connecting with rsh
cvs login server. Default value is `$HOME/.cvspass'. see section Using the client with password authentication
$CVS_CLIENT_LOG.in' and everything sent from the server is logged into `
CVS_IGNORE_REMOTE_ROOThas no effect.
TMPDIR. See section Global options, for a description of how to specify this. Some parts of CVS will always use `/tmp' (via the
tmpnamfunction provided by the system). On Windows NT,
TMPis used (via the
_tempnamfunction provided by the system). The
patchprogram which is used by the CVS client uses
TMPDIR, and if it is not set, uses `/tmp' (at least with GNU patch 2.1). Note that if your server and client are both running CVS 1.9.10 or later, CVS will not invoke an external