      |
|
The following table is an alphabetical list of the configurables that links to details about that configurable.
A — C — D — F — J — L — M — N — R — S — T — Z
| Configurable | Client or Server or Proxy? | Default Value | Meaning | Server Restart Required? |
|---|---|---|---|---|
|
Server |
|
The default method to use for authenticating new users.
|
|
|
Server |
|
An alphanumeric identifier that must be set for all servers in a distributed configuration if you want to implement single login to the master, which is then valid across all replica instances. You must also set |
|
|
Server |
none |
The path to a file that contains one or more PEM-formatted
certificates used to verify the certificate presented by the
AD/LDAP server when using SSL or TLS and
|
|
|
Server |
none |
Specifies the name of the LDAP configuration to use for authentication and the order in which it should be used to search for a given user name. The lowest number confers the highest priority. You may skip numbers. For example: auth.ldap.order.1=UK_LDAP auth.ldap.order.2=US_LDAP auth.ldap.order.5=RU_LDAP If you want LDAP authentication to replace trigger-based authentification, see LDAP authentication in the Helix Core Server Administrator Guide: Fundamentals, and note that the Testing and enabling LDAP configurations procedure requires a server restart. |
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. |
|
Server |
|
Specifies the paging limit for LDAP searches with paged results. Set the configurable to a value less than the result limit of the LDAP server. The default value, |
|
|
Server |
|
Level of SSL certificate validation:
|
|
auth.ldap.timeout
|
Server |
|
The time in seconds to wait before giving up on a connection attempt. |
|
auth.tickets.nounlocked
|
Server | 0
|
If set to 1 means the 2 means the If either value is set, the tagged output from p4 info
shows
that
|
|
|
Server |
|
0 means no automatic creation of users. 1 means that if 2 is similar to |
| Configurable | Client or Server or Proxy? | Default Value | Meaning | Server Restart Required? |
|---|---|---|---|---|
|
Server |
0 |
If a non-zero value, how many seconds to wait before refreshing the list of
Perforce-related
processes running on the
Helix Server. The value of
|
|
|
Server |
256 K |
The value sets the maximum size of memory allotted to
the Setting this configurable to 0 means that the table is written to disk. However, writing the table to memory is recommended to improve performance. If the size of the table exceeds the value of
Note
The value is in database pages of 8 kilobytes. For example, a value of 4096 means 32 MB. See also P4 configure Options and note that |
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. |
|
Server |
|
Enable and configure lockless reads; when enabled, many common commands no longer block other commands attempting to update the database. See the Helix Core Server Administrator Guide: Fundamentals for details. 0: Disable peeking. Behavior is identical to 2013.2 and earlier. 1: New locking order is enabled, peeking is disabled, (diagnostic use only). 2: New locking order is enabled, peeking is
enabled, 3: New locking order is enabled, peeking is
enabled, |
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. |
|
Server |
unset |
Control behavior of commands that access metadata ( readonly: User commands that read metadata are accepted; commands that modify metadata are rejected. Equivalent to starting a replica with the This configurable cannot be set globally; you must specify a server id. |
|
|
Server |
|
Buffer size for journal and checkpoint read/write operations. |
|
|
Server |
|
Set to |
|
|
Server |
none |
Default type for new changelists: either |
|
|
Server |
|
Maximum revision size for |
|
|
Server |
|
Wait this many seconds before forcibly updating an access time, even if server must wait for a lock. |
|
|
Server |
|
Wait this many seconds before requesting a write lock to update an access time. |
|
|
Server |
|
Maximum number of revisions that can be searched with |
|
|
Server |
|
If set to |
|
|
Server |
|
By default, use new integration engine with Sites that wish to continue to use the old (2006.1) integration
logic must set this configurable to 2 by running |
|
|
Server |
|
If set to |
|
|
Server |
|
Default minimum password length for servers where
|
|
|
Server |
|
Allow
Perforce
administrators to use |
|
|
Server |
|
Determine (in accord with the use of IP addresses in the
protections table) whether a user can access a server from a
given IP address. By default, if a connection comes through an
intermediary, the Set this variable to For more information, see the |
|
|
Server |
|
Control behavior of automatic repo creation in a depot of type
0: When a user does a git push, if that repo does not already exist in the graph depot, this new repo is added in the graph depot. 1: When a user does a git push, if that repo does not already exist in the graph depot, the git push fails and the repo is not added to the graph depot. |
|
|
Server |
|
Enable resolve for attributes set with |
|
|
Server |
|
Set to By default, when the journal is rotated, any structured logs are also rotated. Disabling this behavior can help when you’re doing frequent journal rotations and you want the log rotated on a different schedule. |
|
|
Server |
300 seconds |
When a shelf is viewed or modified, update its access time if
its last access time was longer than the limit specified by the
value of Use the |
|
|
Server |
|
Maximum number of files that can be shelved with |
|
|
Server |
|
Maximum size of a file that can be shelved, or |
|
|
Server |
|
Enable to make edge servers always promote shelved files to the
commit server (rather than use the |
|
dm.user.allowselfupdate
|
Server | 1
|
(MFA): The default of To prevent users from changing the value of these variables, set to |
|
|
Server |
|
Wait this many seconds before forcibly updating an access time, even if server must wait for a lock. |
|
|
Server |
|
Wait this many seconds before requesting a write lock to update an access time. |
|
|
Server |
|
Number of password attempts before delay. When the number of consecutive failed login attempts equal this value, a delay is added before next attempt is possible. The delay is 1 second plus 1 second for every next failed attempt up to the maximum of 10 seconds. |
|
|
Server |
|
Control behavior of automatic user creation. 0: Create users as required. When executed by a
nonexistent user, most
Perforce
commands cause a user to be created. An example of a command that
does not create a user is 1: New users may only be created by running 2: New users may only be created by superusers
running |
|
|
Server |
|
If set, all new users created with a password are forced to reset their password before issuing any commands. This configurable applies only if the passwords for newly
created users are set using the |
| Configurable | Client or Server or Proxy? | Default Value | Meaning |
|---|---|---|---|
|
Client |
|
Scan the first |
|
Client, Server |
|
Buffer size for client-side read/write operations. |
|
Server |
|
Use to control symbolic links.
2 same as
3 allows a symlink to a directory that terminates the path without having to use
|
|
Server |
|
Minimum disk space required for any depot before server rejects
commands. (If there is less than To specify size, use the following binary abbreviations, which are slightly different from the more familiar decimal abbreviations: t or You can also use a percentage to specify the relative amount of free disk space required. |
|
Client |
|
Minimum filesize before preallocation (Windows). |
|
Server |
|
Minimum disk space required on server journal filesystem before server rejects commands. To specify size, use the following binary abbreviations, which are slightly different from the more familiar decimal abbreviations: t or You can also use a percentage to specify the relative amount of free disk space required. |
|
Server |
|
Minimum disk space required on server log filesystem before server rejects commands. To specify size, use the following binary abbreviations, which are slightly different from the more familiar decimal abbreviations: t or You can also use a percentage to specify the relative amount of free disk space required. |
|
Server |
|
Minimum disk space required on server root filesystem before server rejects commands. To specify size, use the following binary abbreviations, which are slightly different from the more familiar decimal abbreviations: t or You can also use a percentage to specify the relative amount of free disk space required. |
|
Server |
|
Minimum disk space required for temporary operations before server rejects commands. To specify size, use the following binary abbreviations, which are slightly different from the more familiar decimal abbreviations: t or You can also use a percentage to specify the relative amount of free disk space required. |
|
Server, Client, Proxy |
|
Set to Depending on the depth of your workspace path, this might need to be set on the client, server, and/or proxy (which acts as a client). A file name length of up to 32,767 characters is allowed. Each component of the path is limited to 255 characters. The server root or client root cannot be a long path. |
|
Server |
|
Maximum file size for text type detection. |
| Configurable | Client or Server or Proxy? | Default Value | Meaning |
|---|---|---|---|
|
Server |
unset |
Prefix or directory location for rotated journal. |
| Configurable | Client or Server or Proxy? | Default Value | Meaning | Server Restart Required? |
|---|---|---|---|---|
|
Server |
none |
Lowest version of client software permitted to connect to this
server. The
The value of version can be a version string:
or a client protocol level:
Note
To discover which client protocol version corresponds to a given P4V version string, see the server log. The following server log entry shows that P4V 2017.3 is using v83 as the protocol version: P4V/MACOSX1011X86_64/2017.3/1582486/v83 See also the Support Knowledgebase articles: Tip
We recommend to that you provide your users a message if their client is blocked by this configurable. See |
|
|
Server |
none |
Message to issue if client software is too old, set by
|
|
|
Server |
|
Valid values for the monitor configurable are:
See the |
|
|
Server |
none |
When set on Unix platforms, enables the use of the
$ path/lsof -F pln+
The value for
$ /usr/bin/lsof -F pln
See the |
| Configurable | Client or Server or Proxy? | Default Value | Meaning | Server Restart Required? |
|---|---|---|---|---|
|
Server, Client, Proxy, Broker |
0
|
TCP connection changes to improve performance over long latency connections. To enable, set to See the Support Knowledgebase article, "Autotune - Improved performance over long latency TCP connections". |
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. |
|
Server, Proxy |
|
Maximum length of queue for pending connections. Consider increasing if users find themselves unable to connect to extremely heavily-loaded servers. |
|
|
Server |
|
Number of unacknowledged keepalives before failure. Similar to If See the TCP keepalive section in the Administrators Guide. |
|
|
Server |
|
If If See the TCP keepalive section in the Administrators Guide. |
|
|
Server |
|
Idle time (in seconds) before starting to send keepalives. Similar to If See the TCP keepalive section in the Administrators Guide. |
|
|
Server |
|
Interval (in seconds) between sending keepalive packets. Similar to If See the TCP keepalive section in the Administrators Guide. |
|
|
Proxy |
|
A value in megabytes that controls the proxy’s cache faulting
behavior. A single You must restart the server after changing the value of this configurable. |
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. |
|
Client, Server, Proxy |
unset |
Time, in seconds, before a network connection times out. Best practice is not to set server-wide: if set on
server, requires that users complete command-line forms within
this limit. If set in user’s individual You must restart the server after changing the value of this configurable. |
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. |
|
Server, Proxy |
|
Man-in-the-middle network security level: This enables checks for possible interception or modification of data such as using an SSH tunnel or other TCP forwarder for users with passwords set. 0: Disable MitM checks. 1: Check proxy/broker connections in legacy contexts. 2: Connections from clients are checked for TCP forwarding. 3: Connections from clients, proxies, and brokers are checked for TCP forwarding. 4: All connections are checked; client software older than release 2010.1 cannot connect. 5: Requires that proxies, brokers, and all Perforce intermediate servers have valid logged-in service users associated with them. This allows administrators to prevent unauthorized proxies and services from being used. You must restart the server after changing the value of this configurable. |
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. |
|
Server |
8
|
Specifies the number of files in a batch. See p4 sync on Parallel processing. |
|
|
Server |
|
Specifies the number of bytes in a batch. See p4 sync on Parallel processing. |
|
|
Server |
|
Specifies your maximum number of threads for syncing files concurrently. A value greater than In addition to setting this variable, you must use the
Values can range between Tip
To enable parallel processing, you must set this configurable to a value greater than zero and also greater than or equal to a non-zero value of net.parallel.threads. See also Parallel processing. |
|
|
Server |
|
Specifies the minimum number of files in a parallel sync. A sync that is too small does not initiate parallel file transfers. See p4 sync on Parallel processing. |
|
|
Server |
|
Specifies the minimum number of bytes in a parallel sync. A sync that is too small does not initiate parallel file transfers. See p4 sync on Parallel processing. |
|
|
Server |
|
For automatic parallel processing: specifies the number of files
in a batch. (See also |
|
|
Server |
|
For automatic parallel processing: specifies the number of files
in a batch. (See also |
|
|
Server |
|
For automatic parallel processing: specifies the number of threads to be used for sending files in parallel. The specified
threads grab work in batches. The size of a batch is specified
using the |
|
|
Server |
|
For automatic parallel processing: specifies the number of files in a batch. See the |
|
|
Server |
|
For automatic parallel processing: specifies the minimum number of files to be sent in a parallel submit. See the |
|
|
Server |
|
For automatic parallel processing, specifies the number of threads for sending files in parallel for each submit. The specified threads grab work in batches. The size of a batch is specified using the net.parallel.submit.batch configurable. See the |
|
|
Server |
|
Can help prevent network response degradation. Reduces the number of parallel transmit threads for sync commands when the total
number of concurrent user-transmit threads from all commands, including submit, would exceed the value of this
configurable. Does NOT reduce parallel transmit threads for submit commands.
To determine the value for this configurable, consider the average network utilization of each user-transmit thread and how much spare bandwidth to allocate for occasional peak loads. If parallel syncs are saturating the network, use the p4 monitor |
|
|
Server |
|
Specifies your default number of threads for syncing files concurrently. Tip
To enable parallel processing, you must set this configurable to a value greater than See also Parallel processing. The specified threads grab work in batches. |
|
|
Server |
|
Set You must restart the server after changing the value of this configurable. |
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. |
|
Client, Server |
|
If If an IPv4 literal address (e.g. 127.0.0.1) is used, the
transport is always You must restart the server after changing the value of this configurable. |
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. |
|
Client, Server, Proxy |
|
TCP send and receive buffer sizes, set on connection. Consider increasing for high-latency connections, such as the Proxy. Actual buffer size is the larger of this value and that defined by the OS. You must restart the server after changing the value of this configurable. |
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. |
| Configurable | Client or Server or Proxy? | Default Value | Meaning |
|---|---|---|---|
|
Server |
|
Set to |
|
Server |
none
|
Specifies one or more clients whose requests should be blocked. For more information, see "Blocking Clients" in Helix Core Server Administrator Guide: Fundamentals. |
|
Server |
|
Level of database table checksum verification to perform when rotating journal. Each level corresponds to a larger set of database tables. 0: Disable checksums. 1: Verify the most important system and revision tables. 2: Verify all of level 1, plus tables that hold metadata that does not vary between replicas. 3: Verify all metadata, including metadata that is expected to vary on build-farm and edge-server replicas. |
|
Server |
|
Level of on-the-fly changelist verification to perform. 0: Perform no verification. 1: Write journal note at the end of a submit. 2: Replica verifies changelist summary and writes
to 3: Replica verifies changelist summary and writes
to Setting affects |
|
Server |
|
Level of table checksumming to perform. 0: Perform table-level checksumming only. 1: Journal notes for table-unload and table-scan
are processed by the replica, and are logged to
2: Results of journal note processing in the replica are logged even if the results match. |
|
Server |
|
Enable replica/master network compression: 0: No data stream compression. 1: Data streams used for archive transfer to the
replica ( 2: Data streams used by 3: All data streams ( 4: Compress only the journal pull and journal copy connections between the replica and the master. |
|
Server |
|
Set to For more information, see "Authenticating users" in Helix Core Server Administrator Guide: Multi-Site Deployment. |
|
Server |
|
Used to tune server performance when a forwarding replica has lots of users. Please consult Perforce Support for guidance in adjusting values. |
|
Server |
|
Used to tune server performance when a forwarding replica has lots of users. Please consult Perforce Support for guidance in adjusting values. |
|
Server |
|
Used to tune server performance when a forwarding replica has lots of users. Please consult Perforce Support for guidance in adjusting values. |
|
Server |
|
The number of standby servers that must acknowledge a persisted transaction before the client is notified of successful completion. The default value of 0 means that no standby server has to acknowledge a transaction. See rpl.journal.ack.min. A value of 1 means that one standby has to acknowledge a transaction. Do not set this configurable to a higher value than the number of available standby servers. |
|
Server |
|
Set to Set to |
rpl.journalcopy.location
|
Server |
|
Set to Set to Note that journals written by the journalcopy thread always have their journal number in the suffix. Changing this configurable takes effect when the standby server replicates the P4TARGET's journal rotation. |
|
Server |
|
With a distributed Perforce service, there are both local and global labels. Local labels are restricted to a single edge server, and cannot be used on other servers. Global labels are created and updated on the commit server, and are visible to all servers. However, global labels can only be used with global (unbound) client workspaces. For the 2013.2 release, the default is for labels to be local.
Set When this configurable is set to |
|
Server |
|
Set to one to replicate the The Typically you would not want to replicate this data. But there
are times when this might be needed. For example, if you are
chaining a read-only replica to another replica to provide a warm
standby for failover, you might want your warm standby to
replicate the |
|
Server |
|
Disable default submit archive file copy |
|
Server |
|
If set, a replica server will re-verify the integrity of a cached file every time it delivers the file to the user, If the files do not match, it will re-fetch the file from the upstream server. This is computationally expensive on the replica and typically only useful in conjunction with Perforce technical support. |
|
Server |
|
If set, requires a user to authenticate before running |
| Configurable | Client or Server or Proxy? | Default Value | Meaning | Server Restart Required? |
|---|---|---|---|---|
|
Server |
|
Server security level: 0: Legacy support: passwords not required, strength requirements unenforced. 1: Strong passwords required, existing passwords not reset, compatible with pre-2003.2 client software. 2: Strong passwords required, existing passwords reset, requires 2003.2 or higher client software. 3: Passwords must be strong, and ticket-based
authentication ( 4: All of the above restrictions. Also, authenticated service users must be used for all replica server and remote depot connections to this server. |
|
server
|
Server | 1
|
Server command logging level: -v server=1 ensures that the start information for each command is logged -v server=2 extends server tracing to include command start and stop -v server=3 adds a "compute end" message for certain commands -v server=4 adds errors sent to the client to the server log See also:
|
|
|
Server |
|
Determines whether changes can be fetched.
|
|
|
Server |
|
Determines whether changes can be pushed.
|
|
|
Server |
|
DVCS configurations with files of
type The shared server must be a commit server and this configurable must have To learn about |
|
|
Server |
|
If set to a non-zero value, allows this server to run the |
|
|
Server |
|
Policy for per-command resource limits: 0: All users may use command-line overrides for
1: Per-command options may specify lower, but not higher, resource limits. 2: All command-line resource limit options are silently ignored. |
|
|
Server |
none |
The filesystem location with respect to which a relative address
given in the |
|
|
Server |
0 |
Controls whether the view maps (or client maps) of a non-stream client on an edge server are made global when a client is modified. View maps of a client on a replica must be made global if that client is to be used as a template on another server. This configurable can be set globally, or individually for each server. Setting this configurable can make client
view maps global upon the subsequent client modification . Clearing this configurable does not delete the view
maps of any clients, but does prevent subsequent changes to a
client’s view map from being propagated to other servers. If a
client with global view maps is deleted, its view maps are also
deleted globally regardless of the value of
|
|
|
Server |
1
|
By default, p4 archive and p4 restore lock the global metadata while archiving or restoring revisions. To disable locking, set the value of this configurable to |
|
|
Server |
|
Directory for server locks, specified relative to |
|
|
Server |
|
Set this configurable to |
|
|
Server |
|
When set, the If |
|
|
Server |
|
If monitoring is enabled, and if this configurable is set to a nonzero value, the service refuses to accept more than this many simultaneous command requests. You must restart the server after changing the value of this configurable. |
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. |
n |
Server |
none |
The counter name for the structured log file designated by
See "Logging and structured files" in the Helix Core Server Administrator Guide: Fundamentals for more information. |
|
n |
Server |
none |
Server log file name associated with each structured log file.
See n may not exceed 500. |
|
n |
Server |
none |
For each structured log file, the size, in megabytes, at which the associated log file is rotated. |
|
n |
Server |
none |
For each structured log file, the number of rotated log files to retain on the server at any one time. |
|
|
Server |
none |
The service user as which a server (or proxy) authenticates against a master server in a replication/proxy configuration, or against a remote server in the context of remote depots. |
|
|
Server |
|
Number of buckets (subdirectories) into which files in the spec
depot are hashed. Set to |
|
|
Server |
|
By default,
Perforce’s SSL support
is based on the AES256-SHA cipher suite. To use CAMELLIA256-SHA,
set this tunable to |
|
|
Server and optionally on the client for testing |
|
Controls the TLS version(s) allowed for SSL connections. The connection uses the highest version in common between server and client. ssl.tls.version.min specifies the lowest version,
and Valid values are To see the values on the server:
To set the values on the server, issue commands, then restart the server so the changes take effect. For example, to allow TLSv1.1 or TLSv1.2, but exclude TLSv1.0:
To allow only a single version, assign the same value to both configurables. On a client, to verify that TLSv1.0 does not connect:
|
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. |
|
Server |
none |
For replica servers, set The |
|
|
Server |
|
For replica servers, the file used by the server to track the current journal position. |
|
|
Server |
none |
Enable the generation of global changelist ids. This is relevant for users of the Helix Core Server’s distributed versioning (DVCS) features.
For more information on global changelist ids, see the section "Track a changelist’s identity from server to server" in the "Fetching and Pushing" chapter of Using Helix Core Server for Distributed Versioning. |
|
|
Server |
|
Always re-transfer files after a failed submit. Set this configurable to have the server check whether files are already in the expected archive location and to not re-transfer files when retrying a failed submit. You can override the set behavior by using the
|
|
|
Server |
|
When set, open files that users have locked (with the |
|
|
Server |
|
Limit in microseconds for retrying a failed file rename. Affects
Windows |
|
|
Server |
|
Timeout in microseconds between file rename attempts. Affects
Windows |
| Configurable | Client or Server or Proxy? | Default Value | Meaning |
|---|---|---|---|
|
Server |
none |
Specifies the default client to be used as a template if the
user omits the |
|
Server |
none |
Specifies the default label to be used as a template if the user
omits the |
track
|
Server | none | See "Performance Tracking" in Helix Core Server Administrator Guide: Fundamentals. |
|
Server |
|
If set, specifies that triggers will not receive their parameters via command line variables. Rather, they will receive a dictionary of key/value pairs sent to their STDIN. Triggers can use their dictionary response to reply to the server via STDOUT. |
| Configurable | Client or Server or Proxy? | Default Value | Meaning |
|---|---|---|---|
|
Server |
none |
If set, changes default behavior of |
| |
|