Perforce 2003.2 Command Reference
<< Previous Chapter
P4CLIENT
 Table of Contents
Index
Perforce on the Web
 Next Chapter >>
P4DEBUG

P4CONFIG

Description

Contains a file name without a path. The file(s) it points to are used to store other Perforce environment or registry variables. The current working directory (returned by PWD) and its parents are searched for the file. If the file exists, then the variable settings within the file are used.

The variable settings in the file must sit alone on each line and be in the form variable=value.

Usage Notes

Used by
Client?
 Used by
Server?
 Command-Line Alternative
 Can be set in P4CONFIG file?

Yes

No

None

N/A

Value if not Explicitly Set

Operating System
 Value

All

If not set, this variable is not used.

Examples

A sample P4CONFIG file might contain the following lines:

P4CLIENT=joes_client
P4USER=joe
P4PORT=ida:3548

Notes

P4CONFIG makes it trivial to switch Perforce settings when switching between different projects. If you place a configuration file in each of your client workspaces and set P4CONFIG to point to that file, your Perforce settings will change to the settings in the configuration files automatically as you move from directories in one workspace to another.

You can set the following variables from within the P4CONFIG file:

Perforce 2003.2 Command Reference
<< Previous Chapter
P4CLIENT
 Table of Contents
Index
Perforce on the Web
 Next Chapter >>
P4DEBUG
Please send comments and questions about this manual to [email protected].
Copyright 1999-2003 Perforce Software. All rights reserved.
Last updated: 12/12/03