Windows configuration parameter precedence

Under Windows, Helix Server configuration parameters can be set in many different ways. When a Helix Server application (such as p4 or P4V), or a Helix Server program (p4d) starts up, it reads its configuration parameters according to the following precedence:

  1. For Helix Server applications or a Helix Server (p4d), command-line flags have the highest precedence.
  2. For a Helix Server (p4d), persistent configurables set with p4 configure.
  3. The P4CONFIG file, if P4CONFIG is set.
  4. User environment variables.
  5. System environment variables.
  6. The Windows user registry (or OS X user preferences) (set by p4 set).
  7. The Windows system registry (or OS X 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 with p4 configure have the highest precedence.
  2. Windows service parameters (set by p4 set -S servicename).
  3. System environment variables.
  4. The Windows system registry (or OS X user preferences) (set by p4 set -s).

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

  • The MS-DOS set command
  • The AUTOEXEC.BAT file
  • The User Variables tab under the System Properties dialog box in the Control Panel

System environment variables can be set with:

  • The System Variables tab under the System Properties dialog box in the Control Panel.