Configurables allow you to customize a Perforce service. Configurable settings might affect the server, the client, or a proxy.
Use p4 configure
to set or unset configurables that affect a
Helix Server. These configurables are also described in p4 help
configurables
. For more information on options for setting server configurables and their order of precedence, see p4
configure
.
Changes to most configurables are immediate. However, when you look up a specific configurable under Configurables - alphabetical list, check for the following:
After you change the value of this configurable, you must explicitly "stop" the server.
p4 admin restart is not sufficient.
For UNIX, see Stopping the Perforce Service and Starting the Perforce Service.
For Windows, see Starting and stopping the Helix Server.
You can set configurables that affect the client in the following ways (shown in order of precedence):
As command line global options that are passed at server startup. For example:
$ p4 -u bruno -p perforce:1666 sync
As entries in a P4CONFIG
file. Set configurables like this:
P4USER=bruno P4PORT=perforce:1666
The following configurables can be set in a config file, and you can
also set the variables listed for the p4 help
environment
command:
|
|
|
|
|
|
|
|
|
|
|
|
As entries in a P4ENVIRO
file.
You can use both P4ENVIRO
and P4CONFIG
files to define
environment variables:
P4CONFIG
file for those
variables that have different values for different workspaces P4ENVIRO
file for those variables that remain constant
for all projects. Values set in a P4CONFIG
file override
those set in a P4ENVIRO
file.As set by the p4 set
command for Windows and OS
X. For example:
$ p4 set P4PORT=ssl:tea:1666
You can set configurables that affect the proxy in the following ways:
Using a command line option. For example:
$ p4p -p tcp64:[::]:1999 -t central:1666 -r /var/proxyroot -v proxy.monitor.level=2
On Windows, using the p4 set
command as
follows:
C:\> p4 set -S "perforce_proxy" P4POPTIONS="-v myconfig=myvalue"