Configurables reference
View information about configurables by the Alphabetical list or by the Categories.
To search for information on the page, use the browser search.
Expand a specific section or expand or collapse all sections.
Alphabetical list
Click a letter to view configurables starting with the letter.
A | C | D | F | I | J | L | M | N | P | R | S |T | U | Z
Configurable | Client, server, or proxy? | Default value | Description | Server restart required? |
---|---|---|---|---|
auth.2fa.persist | Server | 1 |
To disable p4 login2 -p, set to 0. To make p4 login-p implicitly invoke p4 login2 -p, set to 2. |
No |
auth.autologinprompt | Server | 1 | The default value causes the command-line user to be prompted to log in. To disable, set to 0 | No |
auth.default.method
|
Server |
|
The default method to use for authenticating new users.
|
No |
auth.id
|
Server |
unset |
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 |
On edge servers (not the master): Yes. See Explicit stop and restart. |
auth.ldap.cafile
|
Server |
unset |
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
|
No |
auth.ldap.order.N
|
Server |
unset |
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, and note that the Testing and enabling LDAP configurations procedure requires a server restart. |
If LDAP Auth is working and you are adding a backup configuration, a restart is not required. However, the following applies after the first valid LDAP configuration is added to the list and after the last LDAP configuration is removed. Yes. See Explicit stop and restart. |
auth.ldap.pagesize
|
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, |
No |
auth.ldap.sslciphers
|
Server |
unset |
SSL ciphers to present to LDAP servers |
Yes. See Explicit stop and restart. |
auth.ldap.ssllevel
|
Server |
|
Level of SSL certificate validation:
|
No |
auth.ldap.timeout
|
Server |
|
The time in seconds to wait before giving up on a connection attempt. |
No |
auth.ldap.userautocreate
|
Server |
|
0 means no automatic creation of users. 1 means that if 2 is similar to |
No |
auth.licenseexpiry.warn
|
Server | 1
|
Enable license expiry warning:
|
No |
auth.licenseexpiry.warnthreshold
|
Server | 7
|
Number of days prior to the expiration of the Helix Core license to start providing the warning if auth.licenseexpiry.warn is set. |
No |
auth.sso.allow.passwd | Server | 0 |
To allow users who authenticate against the Perforce database (as opposed to LDAP or other auth triggers) to fall back to password authentication despite an auth-check-sso trigger being on the server, set to 1 If LDAP is enabled, see the auth.sso.nonldap configurable. See p4 login behavior with auth-check-sso trigger under Single signon and auth-check-sso triggers in Helix Core Server Administrator Guide. |
No |
auth.sso.args | Server | unset |
This configurable can be set to string value to send to the client-side P4LOGINSSO script when an auth-check-sso trigger is in use. This string is substituted for the %ssoArgs% variable in the P4LOGINSSO environment variable, as the client executable is being invoked. For example, the SAML agent can get the identity provider (IdP) URL as follows: p4 configure set auth.sso.args=--idpUrl=yourURLforIdP where --idpUrl=yourURLforIdP replaces %ssoArgs% |
No |
auth.sso.nonldap | Server | 0 |
See p4 login behavior with auth-check-sso trigger under Single signon and auth-check-sso triggers in Helix Core Server Administrator Guide. |
No |
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
|
No |
Configurable | Client, server, or proxy? | Default value | Description | Server restart required? |
---|---|---|---|---|
client.readonly.dir
|
Server |
unset |
The path of the directory on the Helix Core Server for the For example, if |
No |
Server
|
unset |
For parallel sync: To avoid lock contention on the database table used for processing parallel syncs, set the configurable. This specifies the directory that will contain a separate db.sendq table for each client. Consider specifying the same directory you use for client.readonly.dir. |
No |
Configurable | Client, server, or proxy? | Default value | Description | Server restart required? |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
db.checkpoint.bufsize | Server | 224K | Minimum journal buffer size during checkpoint. | No | ||||||||||||
db.checkpoint.numfiles
|
Server | 10
|
Used to determine how many checkpoint files should be generated during a multifile checkpoint operation. See To tune future checkpoint requests. |
No | ||||||||||||
db.checkpoint.reqlevel
|
Server | 4
|
The depth of a table must be greater or equal to this value for it to be considered for splitting. See To tune future checkpoint requests. | No | ||||||||||||
db.checkpoint.threads
|
Server | 0
|
Number of threads to use for checkpoint.
The value can be overridden by the |
No | ||||||||||||
db.checkpoint.worklevel
|
Server | 3
|
The page level examined within a database table that supplies the record keys used to split that table during a multifile checkpoint operation. See To tune future checkpoint requests. |
No | ||||||||||||
db.journalrotate.warnthresh
|
Server | 0
|
If set, to a value between 1 and 365 , at login, if the last journal rotation is older
than the set number of days, a warning reminds admins
and users of type operator to do a journal rotation. |
No | ||||||||||||
db.monitor.addthresh | Server | 0 | The value is in milliseconds. If the value of the monitor is set to 1 or 2, new connections will only be added to the db.monitor table if they run for longer than the number of milliseconds specified in this configurable, or if they become blocked waiting for a lock on a table in the schema. To learn more, see p4 monitor. | No | ||||||||||||
db.monitor.interval
|
Server |
30 since 2018.2 and |
The value of 0 means the feature is off. A non-zero value specifies the number of seconds that the Helix Server waits before checking if any process in the monitor table is marked for termination. If the Helix Server determines that any such process is blocked because it is waiting for client input, the Helix Server terminates it. See also:
|
No | ||||||||||||
db.monitor.shared
|
Server |
|
This configurable is in units of 8 kilobyte pages to be stored in shared memory. The default of 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 that The value is in database pages of 8 kilobytes. See also the Options under the p4 configure command, and note that |
Yes. See Explicit stop and restart. |
||||||||||||
db.monitor.term.allow |
Server |
0
|
To allow users to terminate their own processes, set to A minimum of read permission in the protections table is required for these users to be able to use p4 monitor terminate. |
No | ||||||||||||
db.partition.dropondelete
|
Server | 0
|
If set, during the partitioned client deletion, the individual records are not deleted but the table is deleted followed by the respective journal note. The table cannot be recovered but the performance is improved for the deletion. |
No | ||||||||||||
db.partition.verify
|
Server | 1
|
Enables the verification of partitioned have tables for clients of type |
No | ||||||||||||
db.peeking
|
Server |
|
Enable and configure lockless reads. When enabled, many common commands no longer block other commands attempting to update the database. To learn more, see Commands implementing lockless reads in the Helix Core Server Administrator Guide. 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, To help you decide between 2 and 3, see Possible values for db.peeking in Helix Core Server Administrator Guide. |
Beginning with the 2017.1 release, this configurable is dynamic and no server restart is required. |
||||||||||||
db.peeking.usemaxlock | Server | 0 | When peeking, obey maxlocktime setting. To learn more, see Limiting database queries in Helix Core Server Administrator Guide. | No | ||||||||||||
db.reorg.disable | Server | 1 |
1: The default disables passive B-tree reorganization, which we recommend for solid-state drive (SSD) storage. 0: Enable passive B-tree reorganization. This might:
Changing from the default value is not supported. |
No | ||||||||||||
db.replication
|
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. |
No | ||||||||||||
db.rt.io
|
Server | 0
|
Set to 1 to enable Database IO tracking by the rt.monitorfile configurable. |
Yes. See Explicit stop and restart. |
||||||||||||
dbjournal.bufsize
|
Server |
|
Buffer size for journal and checkpoint read/write operations. |
No | ||||||||||||
dbopen.nofsync
|
Server |
|
For performance, set to |
No | ||||||||||||
defaultChangeType
|
Server |
unset |
Default type for new changelists: either When changes are pushed or fetched, the Type: field for changes ignores the setting of this configurable on the target server. |
No | ||||||||||||
dm.annotate.maxsize
|
Server |
|
Maximum revision size for p4 annotate. | No | ||||||||||||
dm.batch.net
|
Server |
|
Maximum files per (un)lock message sent between edge and commit server. |
No | ||||||||||||
dm.change.skipkeyed
|
Server |
|
When set to These can be
recalculated later with the |
No | ||||||||||||
dm.configure.comment.mandatory
|
Server |
|
If set to |
No | ||||||||||||
dm.domain.accessforce
|
Server |
|
Wait this many seconds before forcibly updating an access time, even if server must wait for a lock. |
No | ||||||||||||
dm.domain.accessupdate
|
Server |
|
Wait this many seconds before requesting a write lock to update an access time. |
No | ||||||||||||
dm.fetch.preservechangenumbers
|
Server | 0
|
If set to 1 , DVCS (or the Distribution Server) preserves existing changelist numbers when pushes or fetches occur. |
No | ||||||||||||
dm.grep.maxrevs
|
Server |
|
Maximum number of revisions that can be searched with |
No | ||||||||||||
dm.info.hide
|
Server |
|
If set to |
No | ||||||||||||
dm.integ.streamspec | Server | 1 |
Changing from the default value is not supported. |
No | ||||||||||||
dm.locks.excl.batch.net
|
Server | 10K
|
Batch size for exclusively (un)locked files sent from an edge to a commit server. See +l at File type modifiers. |
No | ||||||||||||
dm.locks.global.batch.net
|
Server | 10K
|
Batch size for globally (un)locked files sent from an edge to a commit server. See p4 lock -g , p4 fstat -OL , and dm.open.show.globallocks |
No | ||||||||||||
dm.locks.global.result.batch.net
|
Server | 10K
|
Batch size for globally (un)locked files returned from a commit server to an edge server. (See p4 lock -g , p4 fstat -OL , and dm.open.show.globallocks) |
No | ||||||||||||
dm.keys.hide
|
Server |
|
|
No | ||||||||||||
dm.open.show.globallocks
|
Server | 0
|
This is for global locks created through p4 lock, not |
No | ||||||||||||
dm.password.minlength
|
Server |
|
Default minimum password length for servers where
|
No | ||||||||||||
dm.populate.skipkeyed
|
Server | 0 |
0: Recalculates the 1: Unsets the |
No | ||||||||||||
dm.protects.allow.admin
|
Server |
|
Allow
Helix Core
administrators to use Changing from the default value is not supported. |
No | ||||||||||||
dm.protects.exclusioncheck
|
Server | 1
|
Revoking To revert to the legacy behavior (less secure), set this configurable to |
No | ||||||||||||
dm.protects.streamspec
|
Server | 0
|
To start enforcing the stream spec permissions described at p4 protect, set to |
No | ||||||||||||
dm.proxy.protects
|
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. When Helix Core Server evaluates protections table entries, it also considers the setting of the dm.proxy.protects defaults to If For more information, see the |
No | ||||||||||||
dm.repo.noautocreate
|
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. |
No | ||||||||||||
dm.repo.unpack | Server | 1
|
Control the retaining or unpacking of Git packfiles into loose objects when Git Connector imports the contents of an external Git repo into a Helix Core graph depot. The first import creates (or does the initial population of) the repo. Any subsequent imports (or mirroring) append new commits to the repo.
The value of 0 is consistent with the behavior prior to the 2020.2 release. |
No | ||||||||||||
dm.resolve.attrib
|
Server |
|
Enable resolve for attributes set with Changing from the default value is not supported. |
No | ||||||||||||
dm.resolve.ignoredeleted
|
Server | 0 |
When a file has been deleted in branch A and not in branch B,
a merge of B into A results in a conflict, and a
subsequent Changing from the default value is not supported. |
No | ||||||||||||
dm.rotatelogwithjnl
|
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. |
No | ||||||||||||
dm.shelve.accessupdate
|
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 |
No | ||||||||||||
dm.shelve.maxfiles
|
Server |
|
Maximum number of files that can be shelved with |
No | ||||||||||||
dm.shelve.maxsize
|
Server |
|
Maximum size in bytes of a file revision to be shelved, with a valid range from |
No | ||||||||||||
dm.shelve.promote
|
Server |
|
Enable to make edge servers automatically promote shelved files to the
commit server. An alternative is manual promotion with the To determine whether to set this configurable, see Explicitly promoting shelves under Promoting shelved changelist in Helix Core Server Administrator Guide. |
No | ||||||||||||
dm.stream.components
|
Server | 0
|
0 : default, stream components not enabled
See Stream Components in Helix Core Command-Line (P4) Guide. |
No | ||||||||||||
dm.stream.parentview | Server | 0
|
When creating a development, release, or mainline stream without the --parentview parameter, this configurable determines the default value for the ParentView field of the stream spec.
|
No | ||||||||||||
dm.stream.sparse.branchmax
|
Server | 100000
|
Maximum number of depot files in the branch view of a sparse stream.
|
No | ||||||||||||
dm.sync.streamchange
|
Server | 0
|
See the |
No | ||||||||||||
dm.topology.lastseenupdate
|
Server | 300
|
Number of seconds that determines whether to update the |
No | ||||||||||||
dm.user.allowselfupdate
|
Server | 1
|
(MFA): The default of To prevent users from changing the value of these variables, set to |
No | ||||||||||||
dm.user.accessforce
|
Server |
|
Wait this many seconds before forcibly updating an access time, even if server must wait for a lock. |
No | ||||||||||||
dm.user.accessupdate
|
Server |
|
Wait this many seconds before requesting a write lock to update an access time. |
No | ||||||||||||
dm.user.hideinvalid
|
Server | 0
|
Set to 1 to request a password even if the username does not exist. In addition, the security configurable should be set to 1 or higher, and both dm.users.hideinvalid and run.users.authorize should be set to 1 . |
No | ||||||||||||
dm.user.loginattempts
|
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. |
No | ||||||||||||
dm.user.noautocreate
|
Server |
|
Control behavior of automatic user creation. Warning
By default,
Helix Core Server
creates a new user whenever a previously unknown
user invokes any command that can update the repository or its metadata. When executed by a
nonexistent user, most Helix Core Server
commands cause a user to be created. You can control this
behavior by setting the
configurable
with the
$ p4 configure set dm.user.noautocreate=2
|
No | ||||||||||||
dm.user.resetpassword
|
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 |
No | ||||||||||||
dm.user.setinitialpasswd
|
Server |
|
Initial password behavior:
Warning
If this configurable is set to |
No |
Configurable | Client, server, or proxy? | Default value | Description | Server restart required? |
---|---|---|---|---|
filesys.atomic.rename
|
Server |
|
If set to |
Yes |
filesys.binaryscan
|
Client, Server |
|
Scan the first |
No |
filesys.bufsize
|
Client, Server |
|
Buffer size for client-side read/write operations. |
No |
filesys.checklinks
|
Server |
|
Use to control symbolic links. 0: no link checking, so directory 1: blocks attempts to
2: same as
3: allows a symlink to a directory that terminates the path without having to use
|
No |
filesys.depot.min
|
Server |
|
Minimum disk space required for each depot. The server rejects commands from those depots, if any, that fail to meet this minimum. 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. |
No |
filesys.extendlowmark
|
Client |
|
Minimum filesize before preallocation (Windows). |
No |
filesys.P4JOURNAL.min
|
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. |
No |
filesys.P4LOG.min
|
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. |
No |
filesys.P4ROOT.min
|
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. |
No |
filesys.TEMP.min
|
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. |
No |
filesys.windows.lfn
|
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. Changing from the default value is not supported. |
No |
filetype.maxtextsize
|
Server |
|
Maximum file size for text type detection. |
No |
Configurable | Client, server, or proxy? | Default value | Description | Server restart required? |
---|---|---|---|---|
info.p4auth.usercheck
|
Server |
1 |
Validate username against P4AUTH server |
No |
Configurable | Client, server, or proxy? | Default value | Description | Server restart required? |
---|---|---|---|---|
lbr.autocompress
|
Server |
1
|
Specific for the Base filetypes that are stored in RCS format. This excludes
However, any typemap settings set with p4 typemap override this configurable. For example, if a file is specified as type |
No |
lbr.bufsize
|
Server, Proxy |
|
Buffer size for read/write operations to server’s archive of versioned files. |
No |
lbr.proxy.case
|
Proxy |
|
1: File paths are always case-insensitive. 2: File paths are case-insensitive if server is case-insensitive. 3: File paths are always case-sensitive. |
No |
lbr.replica.notransfer
|
Server | 0
|
If set to 1, suppresses direct on-demand file fetch, which forces the use of pull-archive triggers for transfers. See Triggers for external file transfer in Helix Core Server Administrator Guide. | No |
lbr.rcs.existcheck
|
Server | 1
|
Perform RCS validation check during submit | No |
lbr.rcs.maxlen
|
Server | 10M
|
Maximum line length in a +k file. |
No |
lbr.replication
|
Server |
unset |
Define the behavior for replication of versioned files on the Helix Core Server: cache: Replicates version files only when referenced if they do not already exist on the replica. none: Versioned files are not replicated and no user access to versioned files is permitted for read-only replica and read-only standby servers. ondemand: Pulls archives on demand. readonly: Replicates version files when they are updated on the master. shared: For shared storage between a master and replica server, or between a commit server and edge server. To learn more, see Configuring a replica with shared archives in Helix Core Server Administrator Guide. This configurable cannot be set globally. You must specify a server id. |
Yes. See Explicit stop and restart. |
lbr.retry.max
|
Server |
|
In the event of a failed transfer, a replica will make
|
No |
lbr.stat.interval | Server | 0 |
Proxy file status interval. If set to a value, such as 30, the LbrStatus table entry for a large file will be updated every 30 seconds, indicating that the proxy is making progress on the file transfer. If the proxy has not read some data for that file within the 30 seconds then the entry will not be updated. For more information, if you have installed the P4P, see the proxy help by typing at the command line p4p -h |
No |
lbr.storage.allowsymlink |
Server |
0 | To allow symlinks, set to 1 This should only be done if all the symlinks only reference files and directories that are not under any scanned directory. See p4 storage. | No |
lbr.storage.delay | Server | 86400 | Required number of seconds before p4 storage -d scanner considers deleting storage records. 86400 seconds equates to 24 hours. This delay is to allow any in-progress submits and in-progress shelves to complete. | No |
lbr.storage.skipkeyed
|
Server | 2
|
If 2, the default value, no digest is created for keyword revisions and no message is logged. If 1, no digest is created for keyword revisions and a warning message is logged. If 0, a digest is created for all keyword revisions. |
Yes. See Explicit stop and restart. |
lbr.storage.threads
|
Server | 0
|
Number of threads to use for a
|
No |
lbr.verify.in
|
Server |
|
Verify contents from the client to server? ( |
No |
lbr.verify.out
|
Client, Server |
|
Verify contents from the server to client? ( |
No |
lbr.verify.script.out
|
Server |
|
Set to When source watermarking is used, sites have configured a
|
No |
log.originhost
|
Server |
|
Origin and peer IPs in the structured logs. |
No |
Configurable | Client, server, or proxy? | Default value | Description | Server restart required? |
---|---|---|---|---|
minClient
|
Server |
unset |
Lowest version of client software permitted to connect to this server. Consider providing your users a message if their client is blocked by this configurable. See The
The value of version can be a version string:
or a client protocol level:
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: :
|
No |
minClientMessage
|
Server |
unset |
Message to issue if client software is too old, set by
|
No |
monitor
|
Server |
|
Valid values for the monitor configurable are:
See the |
Not for changes between 1 and 25. However, if setting from 0 or to 0, the following applies: Yes. See Explicit stop and restart. |
monitor.lsof
|
Server |
unset |
When set on Unix platforms, enables the use of the
$ path/lsof -F pln
The value for
$ /usr/bin/lsof -F pln
For the list of valid values for this configurable, see the Description of the |
No |
Configurable | Client, server, or proxy? | Default value | Description | Server restart required? | ||||
---|---|---|---|---|---|---|---|---|
net.autotune
|
Server, Client, Proxy, Broker |
1 |
TCP connection changes to improve performance over long latency connections. To disable, set to On Windows-based platforms, send buffer sizes are not autotuned but are manually configurable with net.tcpsize. If net.autotune has a non zero value, the following are ignored:
Autotune defaults to being enabled on Helix Server versions:
Autotune defaults to being disabled on Helix Server versions:
|
Yes. See Explicit stop and restart. |
||||
net.backlog
|
Server, Proxy |
|
Maximum length of queue for pending connections. Consider increasing if users cannot connect to servers that are heavily loaded. |
No | ||||
net.delta.transfer.minsize
|
Client, Server | 128
|
Commits to files of type binary+F use a delta transfer mechanism to only send the modified portion of file content from
the client to the server. This is primarily an optimization for
low-bandwidth remote users, but also helps reduce server-side CPU
usage generally.If 0 on the client, the feature is disabled locally.If 0 on the server, the feature is disabled globally.Other values on the client represent the minimum file size in KB that a delta transfer will be performed on. |
No | ||||
net.delta.transfer.threshold
|
Client | 90
|
Maximum percentage of file size to perform
delta transfer before reverting to streaming
the complete file. |
No | ||||
net.heartbeat.interval
|
Server | 2000
|
Milliseconds between sending heartbeats to the target server. You can interactively invoke p4 heartbeat to observe the effect of varying the value for this configurable. |
The server must be restarted for any background heartbeat threads to start using the updated value for this configurable. |
||||
net.heartbeat.missing.count
|
Server | 5
|
The number of consecutive missed heartbeat responses (see When the count of consecutive missed responses reaches You can interactively invoke p4 heartbeat to observe the effect of varying the value for this configurable. |
The server must be restarted for any background heartbeat threads to start using the updated value for this configurable. |
||||
net.heartbeat.missing.interval
|
Server | 2000
|
Milliseconds between sending heartbeats after a missing response. You can interactively invoke p4 heartbeat to observe the effect of varying the value for this configurable. |
The server must be restarted for any background heartbeat threads to start using the updated value for this configurable. |
||||
net.heartbeat.missing.wait
|
Server | 4000
|
Milliseconds to wait for a response from the target server after a missed response. If the response arrives before the request times out, your You can interactively invoke p4 heartbeat to observe the effect of varying the value for this configurable. |
The server must be restarted for any background heartbeat threads to start using the updated value for this configurable. |
||||
net.heartbeat.wait
|
Server | 2000
|
Milliseconds to wait for a response from the target server. If this interval is exceeded, your You can interactively invoke p4 heartbeat to observe the effect of varying the value for this configurable. |
The server must be restarted for any background heartbeat threads to start using the updated value for this configurable. |
||||
net.keepalive.count
|
Client, Server |
|
Number of unacknowledged keepalives before failure. Similar to If See the TCP keepalive section in the Administrators Guide. |
No | ||||
net.keepalive.disable
|
Client, Server |
|
If If See the TCP keepalive section in the Administrators Guide. |
No | ||||
net.keepalive.idle
|
Client, Server |
|
Idle time (in seconds) before starting to send keepalives. Similar to If See the TCP keepalive section in the Administrators Guide. |
No | ||||
net.keepalive.interval
|
Client, Server |
|
Interval (in seconds) between sending keepalive packets. Similar to If See the TCP keepalive section in the Administrators Guide. |
No | ||||
net.maxclosewait
|
Server | 1000
|
Milliseconds to wait for a network close | No | ||||
net.maxfaultpub
|
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. |
Yes. See Explicit stop and restart. |
||||
net.maxwait
|
Client, Server, Proxy |
0 |
Time, in seconds, before a network connection times out. Note that the default of 0 means the configurable is not activated. 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. |
Yes. See Explicit stop and restart. |
||||
net.mimcheck
|
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. |
Yes. See Explicit stop and restart. |
||||
net.parallel.batch
|
Server |
8
|
Specifies the number of files in a batch. See p4 sync on Parallel processing. |
No | ||||
net.parallel.batchsize
|
Server |
|
Specifies the number of bytes in a batch. See p4 sync on Parallel processing. |
No | ||||
net.parallel.max
|
Server |
|
Specifies your maximum number of concurrent threads for A value greater than In addition to setting this variable, you must also use the
However, If you use
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 Parallel processing for p4 sync, Parallel submits, and Parallel shelving. |
No | ||||
net.parallel.min
|
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. |
No | ||||
net.parallel.minsize
|
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. |
No | ||||
net.parallel.shelve.batch
|
Server |
|
For automatic parallel processing: specifies the number of files
in a batch. (See also |
No | ||||
net.parallel.shelve.min
|
Server |
|
For automatic parallel processing: specifies the minimum number files for auto parallel shelve. A shelf that is too small does not initiate parallel file transfers. (See also |
No | ||||
net.parallel.shelve.threads
|
Server |
0
|
For automatic parallel processing, specifies the number of
threads for sending files in parallel. Can be overridden on the command line, but cannot be greater than net.parallel.max., which must be set to The specified
threads grab work in batches. The size of a batch is specified
using the |
No | ||||
net.parallel.submit.batch
|
Server |
|
For automatic parallel processing: specifies the number of files in a batch. See the |
No | ||||
net.parallel.submit.min
|
Server |
|
For automatic parallel processing: specifies the minimum number of files to be sent in a parallel submit. A submit that is too small does not initiate parallel file transfers. See the |
No | ||||
net.parallel.submit.threads
|
Server |
|
For automatic parallel processing, specifies the number of
threads for sending files in parallel. Can be overridden on the command line, but cannot be greater than net.parallel.max, which must be set to The specified threads grab work in batches. The size of a batch is specified using the net.parallel.submit.batch configurable. See the |
No | ||||
net.parallel.sync.svrthreads
|
Server |
|
Can help prevent the degradation of network response. 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 |
No | ||||
net.parallel.threads
|
Server |
|
Specifies your default number of threads for syncing files concurrently. The specified threads grab work in batches. To enable parallel processing, you must set this configurable to a value greater than |
No | ||||
net.reuseport
|
Server |
|
Set |
Yes. See Explicit stop and restart. |
||||
net.rfc3484
|
Client, Server |
|
|
Yes. See Explicit stop and restart. |
||||
net.tcpsize
|
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. See also net.autotune. |
Yes. See Explicit stop and restart. |
Configurable | Client, server, or proxy? | Default value | Description | Server restart required? |
---|---|---|---|---|
proxy.clearcachethresh
|
Proxy |
|
If set to a value greater than |
No |
proxy.monitor.interval
|
Proxy |
|
Set the proxy monitoring interval. Default is 10 seconds. |
No |
proxy.monitor.level
|
Proxy |
|
0: Monitoring disabled (default). 1: Monitor file transfers only. 2: Monitor all operations. 3: Monitor all traffic for all operations. |
No |
pull.trigger.dir
|
Server |
unset |
Temporary directory for alternative archive copy. |
No |
Server |
|
When set, unlock locked files if p4 push fails. |
No |
Configurable | Client, server, or proxy? | Default value | Description | Server restart required? | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
rcs.nofsync
|
Server |
|
Set to |
No | ||||||||
rejectList
|
Server |
unset
|
Specifies one or more clients whose requests should be blocked. For more information, see Blocking Clients in Helix Core Server Administrator Guide. |
No | ||||||||
rpl.checksum.auto
|
Server |
|
Level of database table checksum verification to perform when rotating a journal. Each level corresponds to a larger set of database tables. 0: Disable checksums. 1: Verify only 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 tables. |
No | ||||||||
rpl.checksum.change
|
Server |
|
Level of on-the-fly changelist verification to perform. 0: Perform no verification. 1: Write a journal note when a 2: Replica verifies changelist summary and writes
to 3: Replica verifies changelist summary and writes
to |
No | ||||||||
rpl.checksum.table
|
Server |
|
Level of table checksumming to perform. 0: Perform table-level checksumming only. 1: When a table is unloaded or scanned, journal notes are written.
These notes are processed by the replica and are logged to
2: When a table is unloaded or scanned, journal notes are written, and the results of journal note processing are logged even if the results match. |
No | ||||||||
rpl.compress
|
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. |
No | ||||||||
rpl.deferred.sends | Server |
|
Allow pull -u threads to fetch missing archives during sync on edge and build servers. 1 is intended to improve performance for syncing from an edge or build server if:
|
No |
||||||||
rpl.forward.all | Server | 0
|
When set to 1 on a replica, commands that are not read-only commands are forwarded to the upstream sever. Instead of setting this configurable, consider setting the Services: field to forwarding-replica in the server spec. See p4 server > Form Fields > Services. |
On the replica server, issue the p4 admin restart command. |
||||||||
rpl.forward.login
|
Server |
|
Set to |
On edge servers (not the master): Yes. See Explicit stop and restart.
|
||||||||
rpl.jnl.batch.size |
Server |
100M |
Maximum size of a single journal transfer in bytes. Limits the amount of data that the target server can send back to journalcopy in a single flush. Set this configurable on the server executing the journalcopy, which is generally a standby server, to tune the maximum size of journal fragments sent to journalcopy. |
The following applies to the server that executes the journalcopy: Yes. See Explicit stop and restart. |
||||||||
rpl.jnlwait.adjust
|
Server |
|
The additional time in milliseconds to add to the wait before checking for journal updates after no updates were seen. The total will not exceed the value specified by |
No | ||||||||
rpl.jnlwait.interval
|
Server |
|
The longest time in milliseconds to wait before checking for journal updates. Incremented by |
No | ||||||||
rpl.jnlwait.max
|
Server |
|
The longest time in milliseconds to wait before checking for journal updates. For guidance in adjusting values, contact Perforce Support. |
No | ||||||||
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. |
No | ||||||||
rpl.labels.global
|
Server |
|
A multi-site deployment supports both local and global labels.
To learn more, see Commit-edge in Helix Core Server Administrator Guide. |
No | ||||||||
rpl.pull.archivedepots | Server | 0 | To enable the propagation of archive files to a replica, such as a standby server, set this to 1 | On edge servers (not the master):
Yes. See Explicit stop and restart. |
||||||||
rpl.pull.position | Server |
|
Interval in milliseconds for pull position reports. If set, the position in the P4TARGET's journal of the last journal fragment applied by the replica is written (that is, reported) to the replica's server log and the replica's journal at the specified interval. |
For most installations, changes take effect within a few minutes, provided the configurable was set when the replication thread was started. For all installations, changes take effect when the replication thread is restarted, which typically necessitates restarting the replica for which this configurable was changed. |
||||||||
rpl.replay.userrp
|
Server |
|
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 |
No | ||||||||
rpl.submit.nocopy
|
Server |
|
Disable default submit archive file copy |
No | ||||||||
rpl.track.behind
|
Server |
|
If set, report journals/total bytes not replicated
|
Yes. See Explicit stop and restart. |
||||||||
rpl.track.behind.interval
|
Server |
|
Maximum interval in milliseconds for pull lag reports. The default is the equivalent of 10 seconds. |
Yes. See Explicit stop and restart. |
||||||||
rpl.pull.reload
|
Server | 6000
|
Interval in milliseconds for p4 pull to reload any configuration changes. |
No | ||||||||
rpl.verify.cache
|
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. |
No | ||||||||
rt.monitorfile
|
Server | unset |
Enable real-time monitoring of server performance, if this configurable is set to specify a file that backs the shared memory. For example,
The real-time monitoring output cannot be viewed from a text editor. However, you can display real-time monitoring values on the command line by using any of the following:
See also p4 monitor realtime. |
Yes. See Explicit stop and restart. |
||||||||
run.clientexts.allow
|
Server |
|
Allow client-side Extensions to run. |
No | ||||||||
run.renameclient.allow
|
Server | 1
|
Allow the p4 renameclient command.
|
No | ||||||||
run.unzip.user.allow
|
Server | 0
|
Should p4 unzip allow -u |
No | ||||||||
run.users.authorize
|
Server |
|
If set to 1, requires a user to authenticate before running the |
No |
Configurable | Client, server, or proxy? | Default value | Description | Server restart required? |
---|---|---|---|---|
security
|
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. 5: Requires that any intermediary (such as a proxy or broker) has a valid authenticated service user. 6: Requires each intermediary to have a valid server spec, where the service user must match the user named in the User field of the spec. For details, see Server security levels in Helix Core Server Administrator Guide. |
No |
server
|
Server | 1
|
Server command logging level: server=1 ensures that the start information for each command is logged server=2 extends server tracing to include command start and stop server=3 adds a compute end message and Sync Network Estimates for p4 sync server=4 adds errors sent to the client See also Diagnostic flags for monitoring the server in Helix Core Server Administrator Guide and P4LOG |
No |
server.allowfetch
|
Server |
|
Determines whether changes can be fetched.
|
No |
server.allowpush
|
Server |
|
Determines whether changes can be pushed.
|
No |
server.allowremotelocking
|
Server |
|
DVCS configurations with files of
type The shared server must be a commit server and this configurable must have See |
No |
server.allowremotelocking
|
Server |
|
DVCS configurations with files of
type The shared server must be a commit server and this configurable must have See |
No |
server.commandlimits
|
Server |
|
Policy for per-command resource limits: 0: All command-line users can override these
limits in 1: Per-command options can specify lower, but not higher, resource limits. 2: All command-line resource limit options are silently ignored and the spec limits are not overridden. |
No |
server.depot.root
|
Server |
unset |
The filesystem location, an absolute path, with respect to which a relative address
given in the |
No |
server.extensions.allow.admin
|
Server | 1
|
0: Prevents
|
Yes. See Explicit stop and restart. |
server.extensions.allow.unsigned
|
Server | 0
|
|
Yes. See Explicit stop and restart. |
server.extensions.dir
|
Server |
|
Directory for Extension-owned storage, which defaults to P4ROOT/server.extensions.dir |
No |
server.global.client.views
|
Server |
|
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
|
No |
server.locks.archive
|
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 |
No |
server.locks.dir
|
Server |
|
Directory for server locks, specified relative to |
No |
server.locks.global
|
Server |
|
Set this configurable to |
No |
server.locks.sync
|
Server |
|
When set, the If |
No |
server.maxcommands
|
Server |
|
If monitoring is enabled, this configurable is set to a nonzero value, and the limit is exceeded, p4d refuses to accept more than this many simultaneous command requests and users receive the TooManyCommands error. See server.maxcommands.allow. |
Yes. See Explicit stop and restart. |
server.maxcommands.allow | Server | 1 |
Enables super and operator users to access to a subset of commands, even if server.maxcommands is reached. See Commands that super and operator users can always run under Limiting simultaneous connections in the Helix Core Server Administrator Guide. To disable, set to 0. |
Yes. See Explicit stop and restart. |
server.rolechecks
|
Server | 0 | Should p4d enforce p4 server settings. |
No |
serverlog.bufsz.N
|
Server |
unset
|
Unset: By default, there is no buffer.
|
No |
serverlog.counter.
|
Server |
unset |
Rarely used because if unset, p4d controls the rotated log names, which are incremented from |
No |
serverlog.file.
|
Server |
unset |
Server log file name associated with each structured log file.
See |
No |
serverlog.maxmb.
|
Server |
unset |
For each structured log file, the size, in megabytes, at which the associated log file is rotated. |
No |
serverlog.retain.
|
Server |
unset |
For each structured log file, the number of rotated log files to retain on the server at any one time. |
No |
serverlog.version.
|
Server | the current server protocol level |
The serverlog version matches a server protocol level and retains a level prior to an upgrade. See Protocol levels: server/client in Helix Core Server Administrator Guide. |
No |
serviceUser
|
Server |
unset |
The service user that represents a server or proxy when authenticating against a master server, or a remote server. |
No |
spec.hashbuckets
|
Server |
|
Maximum number of subdirectories for hashed directory structures. This limits the number of subdirectories into which files are hashed in the spec depot - see Working with spec depots, unload depot - see Unloading infrequently-used metadata in the Helix Core Server Administrator Guide, and the server.locks.dir directory.
|
No |
ssl.cipher.list
|
Server | unset | The list of OpenSSL ciphers p4d allows when establishing a connection at TLS 1.2 or below, overriding the OpenSSL defaults. |
Yes. See Explicit stop and restart. |
ssl.cipher.suites
|
Server | unset | The list of OpenSSL cipher suites p4d allows when establishing a TLS 1.3 connection, overriding the OpenSSL defaults |
Yes. See Explicit stop and restart. |
ssl.client.ca.path
|
Client, Server | unset |
Can be set on a client, including a p4d that acts as a client to another p4d. The path of the Certificate Authority (CA) Privacy-Enhanced Mail (PEM) file to validate the server certificate. The certificate authority (CA) path can be specified with this client-side configurable if the CA is not present in the system's CA store or if validation against a specific CA is required. |
Yes. See Explicit stop and restart. |
ssl.client.cert.validate
|
Client, Server | 1
|
Can be set on a client, including a p4d that acts as a client to another p4d. |
Yes. See Explicit stop and restart. |
ssl.client.tls.version.min
|
Client, Server | 12
|
Can be set on a client, including a server, broker, or proxy that acts as a client to another server. Determines which TLS versions the client allows for SSL connections. The
connection uses the highest version in common between Server and
client. These client and server configurables can be used in servers, proxies, or brokers where both upstream (client-side) and downstream (server-server) connections are made. For example, in edge-to-edge chaining, one edge server acts as a client to another edge server. This aspect of a server as a client applies to other scenarios as well, such as centralized authorization server (P4AUTH), centralized changelist server (P4CHANGE), and when one server accesses a remote depot on another server. |
Yes. See Explicit stop and restart. |
ssl.client.tls.version.max
|
Client, Server | 13
|
Can be set on a client, including a server, broker, or proxy that acts as a client to another server. Determines which TLS version(s) the client allows for SSL connections. The
connection uses the highest version in common between Server and
client. These client and server configurables can be used in servers, proxies, or brokers where both upstream (client-side) and downstream (server-server) connections are made. For example, in edge-to-edge chaining, one edge server acts as a client to another edge server. This aspect of a server as a client applies to other scenarios as well, such as centralized authorization server (P4AUTH), centralized changelist server (P4CHANGE), and when one server accesses a remote depot on another server. |
Yes. See Explicit stop and restart. |
ssl.client.trust.name
|
Client | 1
|
If you run p4 trust against a server that has a certificate that is not self-signed,
|
No |
ssl.secondary.suite
|
Server |
|
|
No |
Server and optionally on the client for testing | 12 |
Determines which TLS versions the server, broker, or proxy allows for SSL connections. The connection uses the highest version in common between the server, broker, or proxy and its client. See also the corresponding client-side configurables: ssl.client.tls.version.min and ssl.client.tls.version.max. |
Yes. See Explicit stop and restart. |
|
Server and optionally on the client for testing |
|
Determines which TLS versions the server, broker, or proxy allows for SSL connections. The connection uses the highest version in common between the server, broker, or proxy and its client. See also the corresponding client-side configurables: ssl.client.tls.version.min and ssl.client.tls.version.max. ssl.tls.version.min specifies the lowest version that the server, broker, or proxy allows, and Valid values are For security, choose a value that is at least |
Yes. See Explicit stop and restart. |
|
startup.N
|
Server |
unset |
For replica servers, set |
Yes. See Explicit stop and restart. |
statefile
|
Server |
|
For replica servers, the file used to track the current journal position. |
No |
submit.allowbgtransfer | Server | 0 |
To enable background archive transfer, set to 1 on those edge servers. To cause the commit server's
p4 sync command to wait for the completion of queued background file transfer for files submitted from edge servers, set to See submit.autobgtransfer and Background archive transfer for edge server submits in Helix Core Server Administrator Guide. |
Yes. See Explicit stop and restart. |
submit.autobgtransfer | Server | 0 |
If you have set submit.allowbgtransfer to 1 on one or more the edge servers that participate in your replicated environment, to make p4 submit function as if it were an alias for p4 submit -b on those edge servers, also set |
Yes. See Explicit stop and restart. |
submit.collision.check | Server | 1 |
The default, 1, prevents submitting a changelist that contains what the server perceives as a name collision between directory name and file name. To remove the check, set this configurable to 0 and be aware of the risk of accidentally overwriting file content. |
No |
submit.identity
|
Server |
unset |
Enable the generation of global changelist ids for DVCS: uuid generates the id in uuid format, checksum generates the id in checksum format, serverid generates the id in serverid+change format. See Track a changelist’s identity from server to server in Using Helix Core Server for Distributed Versioning. |
No |
submit.noretransfer
|
Server |
|
1: Check whether files are already in the expected archive location and not re-transfer such files. You can override the set behavior by using the
|
Yes. See Explicit stop and restart. |
submit.storagefields
|
Server |
|
Regarding the |
No |
submit.unlocklocked
|
Server |
|
If set, open files that users have locked (with the |
No |
sys.pressure.max.pause.time
|
Server | 300
|
If set, the number of seconds a command can be in the paused state before an error returns to the client. Setting this configurable to 0 disables pausing commands. For all the sys.pressure.* configurables, see System resources in Helix Core Server Administrator Guide. |
No |
sys.pressure.max.paused
|
Server | 1000
|
If set, the maximum number of concurrently-paused client commands. New incoming commands above this threshold are rejected with an error. For all the sys.pressure.* configurables, see System resources in Helix Core Server Administrator Guide. |
No |
sys.pressure.mem.high
|
Server | 95
|
If set, while the server is above this threshold, commands might be canceled and return an error to the client. For all the |
No |
sys.pressure.mem.high.duration
|
Server | 1000
|
Number of milliseconds for averaging sys.pressure.mem.high . For all the sys.pressure.* configurables, see System resources in Helix Core Server Administrator Guide. |
No |
sys.pressure.mem.medium
|
Server | 80
|
If set, when commands begin pausing. For all the sys.pressure.* configurables, see System resources in Helix Core Server Administrator Guide. |
No |
sys.pressure.os.cpu.high
|
Server | 100
|
(Linux) CPU monitoring is only available if cgroups v2 support is configured. This configurable represents the amount of time some processes on the system are stalled waiting for CPU time. For Linux cgroup support, only the system-wide /proc/pressure/* files are considered. For all the sys.pressure.* configurables, see System resources in Helix Core Server Administrator Guide. |
No |
sys.pressure.os.cpu.high.duration
|
Server | 2000
|
Number of milliseconds for averaging sys.pressure.os.mem.high . For all the sys.pressure.* configurables, see System resources in Helix Core Server Administrator Guide. |
No |
sys.pressure.os.mem.high
|
Server | 70
|
(Windows and Linux) Amount of time some processes on the system are stalled waiting for memory. New incoming commands received by p4d are rejected. Existing commands that request more memory might be canceled and return an error to the client. When p4d limits its work, it does not distinguish between memory used by other processes on the operating system and its own. For example, if a large external process comes and consumes a large amount of memory, p4d can throttle itself. For all the sys.pressure.* configurables, see System resources in Helix Core Server Administrator Guide. |
No |
sys.pressure.os.mem.high.duration
|
Server | 2000
|
Number of milliseconds for averaging sys.pressure.mem.high . For all the sys.pressure.* configurables, see System resources in Helix Core Server Administrator Guide. |
No |
sys.pressure.os.mem.medium
|
Server | 40
|
(Linux) The server tries to keep memory usage below this level. For all the sys.pressure.* configurables, see System resources in Helix Core Server Administrator Guide. |
No |
sys.pressure.os.mem.medium.duration
|
Server | 2000
|
Number of milliseconds for averaging sys.pressure.os.mem.medium . For all the sys.pressure.* configurables, see System resources in Helix Core Server Administrator Guide. |
No |
sys.rename.max
|
Server and client |
|
Limit for the number of retries to rename a file if renaming fails. Affects
Windows |
No |
sys.rename.wait
|
Server and client |
|
Timeout in microseconds between file rename attempts. Affects
Windows |
No |
sys.threading.groups | Server | 0 | If set to 1, adds support for utilizing multiple processor groups. |
Yes. See Explicit stop and restart. |
Configurable | Client, server, or proxy? | Default value | Description | Server restart required? |
---|---|---|---|---|
template.client
|
Server |
unset |
Specifies the default client to be used as a template if the
user omits the |
No |
template.label
|
Server |
unset |
Specifies the default label to be used as a template if the user
omits the |
No |
track
|
Server | Set by the server. See Performance Tracking under Diagnostic flags for monitoring the server in Helix Core Server Administrator Guide. | No | |
trait.storagedepot.min
|
Server | 0
|
If unset or set to If set to a value greater
than Retrieving trait values from the See also Attribute values and the trait depot in the p4 attribute topic. |
No |
triggers.io
|
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. |
No |
Configurable | Client, server, or proxy? | Default value | Description | Server restart required? |
---|---|---|---|---|
unicode
|
Server |
unset |
If set, the server will assume all data is encoded in utf8 and enable file content translation for files of type Unicode mode cannot be disabled and should only be enabled by the |
Yes. See Explicit stop and restart. |
Configurable | Client, server, or proxy? | Default value | Description | Server restart required? |
---|---|---|---|---|
zerosyncPrefix
|
Server |
unset |
If set, changes default behavior of |
No |
zlib.compression.level
|
Server, Client | unset |
Provides a way to find a balance between file size and compression time:
|
No |
Categories
A configurable can be in one or more categories. For example, a configurable in the Security and Performance categories might affect security and performance.
Items in all capital letters are Environment and registry variables, not configurables.
You can also view configurables by the Alphabetical list.
Explicit stop and restart
Some configurables have Yes in the Server restart required column. Changes to those configurables do not take effect unless you explicitly "stop" the server. The p4 admin restart command is not sufficient.
For UNIX, see Stopping the Perforce Service and Starting the Perforce Service.
For Windows, see Starting and stopping the Helix Core Server.