Configurables

Configurables allow you to customize a Helix Core service.

Configurables that affect the server
Configurables that affect the client
Configurables that affect the proxy

To see details about a configurable, click a letter:

A — C — D — F — J — L — M — N — P — R — S — T — U — Z

Configurables that affect the server

p4 configure show displays the current configuration of this server.

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.

Tip

The DistributedConfig field of the server spec shows a line for each configurable that is set to a non-default value. In this field, you can edit the value, add a new line to set a different configurable to a non-default value, or delete a line to reset that configurable to its default value.
p4 configure history allows the super user to track the history of changes to the values of configurables.

server restart

Most configurables can be set dynamically. A subset of the configurables require the server to be stopped and restarted. In the alphabetical list of configurables, look for this Note:

After you change the value of this configurable, you must explicitly "stop" the server.

Note
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.

Configurables that affect the client

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:
- filesys.binaryscan, filesys.bufsize
- lbr.verify.out
- net.keepalive.count, net.keepalive.disable, net.keepalive.interval, net.maxwait, net.rfc3484, net.tcpsize,
- sys.rename.max, sys.rename.wait
As entries in a P4ENVIRO file.

You can use both P4ENVIRO and P4CONFIG files to define environment variables:
- use the P4CONFIG file for those variables that have different values for different workspaces
- use the 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 macOS. For example:
```
$ p4 set P4PORT=ssl:tea:1666
```

Configurables that affect the proxy

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

Using environment variables

On Windows, using the p4 set command:

C:\> p4 set -S "perforce_proxy" P4POPTIONS="-v myconfig=myvalue"