Environment and Registry Variables

Perforce 2000.2 Command Reference (2000.2.cr.1)


<< Previous Chapter p4 where	Table of Contents Index Perforce on the Web	Next Chapter >> P4CLIENT

Environment and Registry Variables

Each operating system and shell has its own syntax for setting environment variables. The following table shows how the P4CLIENT environment variable is set in each OS and shell:


OS or Shell	Environment Variable Example
UNIX: `ksh`, `sh`, `bash`	`export P4CLIENT=value`
UNIX: `csh`	`setenv P4CLIENT value`
VMS	`def/j P4CLIENT "value"`
Mac MPW	`set -e P4CLIENT value`
Windows 95/98/NT/2000	`p4 set P4CLIENT=value` (See the `p4 set` chapter of this manual for more details on setting Perforce's registry variables in Windows). NT administrators running Perforce as a service can set variables for use by a specific service with `p4 set -S` `svcname` `var=value`.

Perforce's environment variables can be loosely grouped into the following four categories:

Crucial: The variable will almost definitely need to be set on the client; the default values will rarely be sufficient. Understanding these variables is crucial for users and administrators alike.
Useful: Setting this variable can provide additional functionality to the user, but is not required for most Perforce operations.
Esoteric: The default value of this variable should be sufficient; it will rarely need to be changed.

Server: The variable is set by the Perforce system administrator on the machine running the Perforce server. Some of these variables are used by Perforce clients as well; in these cases, the variable is categorized twice.


Crucial Variables	Useful Variables	Esoteric Variables	Server Variables
`P4CLIENT`	`P4CONFIG`	`P4PAGER`	`P4JOURNAL`
`P4PORT`	`P4DIFF`	`PWD`	`P4LOG`
`P4PASSWD`	`P4EDITOR`	`TMP, TEMP`	`P4PORT`
`P4USER`	`P4MERGE`		`P4ROOT`
			`P4DEBUG`

Perforce 2000.2 Command Reference (2000.2.cr.1)


<< Previous Chapter p4 where	Table of Contents Index Perforce on the Web	Next Chapter >> P4CLIENT