Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 Server Administration Documentation | 2025.2

# Configuration parameter precedence

Configuration parameters for P4D, P4 and P4V can be set in different ways. The following precedence applies, where 1 overrides 2, 2 overrides 3, and so on:

1. For P4 Server applications or a P4 Server (`p4d`), command-line flags, but these are not a persistent configuration.
2. For a P4 Server (`p4d`), persistent configurables set by `p4 configure` or within the DistributedConfig form field of the p4 server spec.
3. The `P4CONFIG` file, if `P4CONFIG` is set.
4. User environment variables. See P4ENVIRO.
5. System environment variables.
6. Windows user registry or macOS user preferences set by `p4 set`.
7. Windows system registry or macOS system preferences (set by `p4 set -s`).

When a Perforce service (`p4s`) starts up, it reads its configuration parameters from the environment according to the following precedence:

1. Persistent configurables set by `p4 configure` or within the DistributedConfig form field of the p4 server spec.
2. Windows service parameters set by `p4 set -S `servicename``
3. System environment variables.
4. Windows system registry or macOS user preferences (set by `p4 set -s`).

User environment variables can be set with any of the following:

- Linux `export`, Windows command prompt `set`
- The `AUTOEXEC.BAT` file
- Windows User Variables tab under the System Properties dialog box in Control Panel

System environment variables can be set with:

- Linux `export`, Windows System Variables tab under the System Properties dialog box in the Control Panel.

The output of `p4 set` lists the value of each variable and how each variable was set, such as by `config`, `enviro`, `set`, or `set -s`

Your search for returned results