Configurables - alphabetical list

auth.2fa.persist
auth.autologinprompt
auth.default.method
auth.id
auth.ldap.cafile
auth.ldap.order.N
auth.ldap.pagesize
auth.ldap.ssllevel
auth.ldap.timeout
auth.tickets.nounlocked
auth.ldap.userautocreate
auth.sso.allow.passwd
auth.sso.args
auth.sso.allow.nonldap

client.readonly.dir
client.sendq.dir

db.monitor.interval
db.monitor.shared
db.peeking
db.replication
dbjournal.bufsize
dbopen.nofsync
defaultChangeType
dm.annotate.maxsize
dm.domain.accessforce
dm.domain.accessupdate
dm.grep.maxrevs
dm.info.hide
dm.integ.engine
dm.keys.hide
dm.password.minlength
dm.protects.allow.admin
dm.proxy.protects
dm.resolve.attribs
dm.rotatelogwithinjnl
dm.shelve.accessupdate
dm.shelve.maxfiles
dm.shelve.maxsize
dm.shelve.promote
dm.user.accessforce
dm.user.accessupdate
dm.user.loginattempts
dm.user.allowselfupdate
dm.user.noautocreate
dm.user.resetpassword

filesys.binaryscan
filesys.bufsize
filesys.checklinks
filesys.depot.min
filesys.extendlowmark
filesys.P4JOURNAL.min
filesys.P4LOG.min
filesys.P4ROOT.min
filesys.TEMP.min
filesys.windows.lfn
filetype.maxtextsize

journalPrefix

lbr.autocompress
lbr.bufsize
lbr.proxy.case
lbr.replica.notransfer
lbr.replication
lbr.retry.max
lbr.verify.in
lbr.verify.out
lbr.verify.script.out

minClient
minClientMessage
monitor
monitor.lsof

net.autotune
net.backlog
net.keepalive.count
net.keepalive.disable
net.keepalive.idle
net.keepalive.interval
net.maxfaultpub
net.maxwait
net.mimcheck
net.parallel.batch
net.parallel.batchsize
net.parallel.max
net.parallel.min
net.parallel.minsize
net.parallel.shelve.batch
net.parallel.shelve.min
net.parallel.shelve.threads
net.parallel.submit.batch
net.parallel.submit.min
net.parallel.submit.threads
net.parallel.sync.svrthreads
net.parallel.threads
net.reuseport
net.rfc3484
net.tcpsize

proxy.monitor.interval
proxy.monitor.level
pull.trigger.dir

To disable p4 login2 -p, set to 0.

To make p4 login -p implicitly invoke p4 login2 -p, set to 2.

Server

perforce

The default method to use for authenticating new users.

• perforce specifies that the user is to be authenticated using the db.user table. This is the default setting.

  If there are no active LDAP configurations, this setting might cause a new user to be authenticated against an AD/LDAP server, using an authentication trigger if such a trigger exists.

• ldap specifies the user be authenticated in against an AD/LDAP server without having to use authentication triggers.

  In addition, if you want new users to be automatically created when they have successfully authenticated against an AD/LDAP server, set the configurable auth.ldap.userautocreate to a non-zero value.

Server

0

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 rpl.forward.login to one for each replica participating in the distributed configuration.

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 auth.ldap.ssllevel is >=1.

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.

Server

0

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, 0, means that paging is not enabled.

Server

0

Level of SSL certificate validation:

• 0: No validation; default.
• 1: Certificate must be valid, but the common name is not checked.
• 2: Certificate must be valid and the certificate common name matches the AD/LDAP server’s host name.

Server

30

The time in seconds to wait before giving up on a connection attempt.

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 the Administrator Guide on "Single signon and auth-check-sso triggers", which discussed "p4 login behavior with auth-check-sso trigger".

This configurable is designed for invoking the client-side Desktop Agent for single sign-on (SSO).

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%

• When set to 0 and LDAP authentication is enabled, users whose AuthMethod is perforce will authenticate by password against the Perforce database.
• If set to 1, those users will be required to authenticate using a client-side P4LOGINSSO script.

• Note: If this configurable and auth.sso.allow.passwd are both set to 1, users whose AuthMethod is perforce will be able to authenticate using a client-side P4LOGINSSO script, or fallback to authenticating by password against the Perforce database.

See the Administrator Guide on "Single signon and auth-check-sso triggers", which discusses "p4 login behavior with auth-check-sso trigger".

If set to 1 or 2, prevents p4 login -a from issuing host unlocked tickets. In other words, 1 or 2 enforce host locked tickets, which are restricted to the one host with the correct IP address.

1 means the -a flag is silently ignored and the users are always issued host locked tickets.

2 means the -a flag is explicitly disabled and users get an error if they try to use it.

If either value is set, the tagged output from p4 info

p4 -ztag info

shows that unlockedTickets is disabled:

... unlockedTickets disabled

Server

none

Server

30 in 2018.2 and 0 prior to 2018.2

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:

• "Enabling process monitorning" in the Helix Core Server Administrator Guide: Fundamentals
• the Support Knowledgebase article, "Fixing a hung Helix Server server"

Server

256 K

The value sets the maximum size of memory allotted to the db.monitor table, which tracks the p4d commands that are currently running.

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 db.monitor.shared, an error is returned. Commands are still executed, but they are not recorded in the table.

Server

2

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, hx/dx optimization on.

3: New locking order is enabled, peeking is enabled, hx/dx optimization is off.

Server

unset

Control behavior of commands that access metadata (db.* files) on the Helix Server server:

readonly: User commands that read metadata are accepted; commands that modify metadata are rejected.

Equivalent to starting a replica with the p4d -M readonly option.

This configurable cannot be set globally; you must specify a server id.

Server

16K

Buffer size for journal and checkpoint read/write operations.

Server

0

Set to 1 to disable fsync() call when server closes a db.* database file, and permit the OS to determine when to write the modified data.

Server

none

Default type for new changelists: either public or restricted. If unset, new changelists are public.

Server

10M

Maximum revision size for p4 annotate.

Server

3600

Wait this many seconds before forcibly updating an access time, even if server must wait for a lock.

Server

300

Wait this many seconds before requesting a write lock to update an access time.

Server

10K

Maximum number of revisions that can be searched with p4 grep.

Server

0

If set to 1, and the user is not authenticated, p4 info hides:
Server name
Server address
Server uptime
Server license ip address
and the license string is either none or Licensed.

Server

3

By default, use new integration engine with p4 integrate. (The p4 merge command always uses the v3 integration engine regardless of this setting.)

Sites that wish to continue to use the old (2006.1) integration logic must set this configurable to 2 by running p4 configure set dm.integ.engine=2.

Server

0

If set to 1 or 2, p4 keys requires admin access. If set to 2, p4 key requires admin access.

Server

8

Default minimum password length for servers where security is set to a nonzero value.

Server

0

Allow Perforce administrators to use -a, -g, and -u with p4 protects. By default, only superusers can use these options.

Server

1

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 proxy- prefix is prepended to the client IP address.

Set this variable to 0 if you do not want to have connections that come in through an intermediary to have the proxy- prefix.

For more information, see the p4 protect command.

Server

0

Control behavior of automatic repo creation in a depot of type graph.

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

1

Enable resolve for attributes set with p4 attribute.

Server

1

Set to 0 to disable log rotation after journal rotation.

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 dm.shelve.accessupdate

Use the p4 -Ztag change -o command to display the access time for shelved files.

Server

10M

Maximum number of files that can be shelved with p4 shelve.

Server

0

Maximum size of a file that can be shelved, or 0 for unlimited.

Server

0

Enable to make edge servers always promote shelved files to the commit server (rather than use the -p option). Generally, it is a bad idea to enable automatic promotion because it causes a lot of unnecessary file transfers for shelved files that are not meant to be shared.

(MFA): The default of 1 allows a user to set the value of her or his %email% and %fullname% variables.

To prevent users from changing the value of these variables, set to 0.

Server

3600

Wait this many seconds before forcibly updating an access time, even if server must wait for a lock.

Server

300

Wait this many seconds before requesting a write lock to update an access time.

Server

3

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

0

Control behavior of automatic user creation.

$ p4 configure set dm.user.noautocreate=2

Client

64K

Client, Server

4K

Server

0

Server

250M

Client

32K

Server

250M

Server

250M

Server

250M

Server

250M

Server, Client, Proxy

1

Server

0

Server, Proxy

4K

Proxy

1

Server

unset

Server

50

Server

1

Client, Server

1

Server

none

Lowest version of client software permitted to connect to this server. The minClient version can be lower than, or equal to, the server version, but not higher than the server version. The syntax to set this configurable is:

p4 configure set minClient=version

The value of version can be a version string:

p4 configure set minClient=2017.2

or a client protocol level:

p4 configure set minClient=83

See also the Support Knowledgebase articles:

• "How to force users to upgrade their client software"
• "Helix Client Protocol Levels"

Server

none

Message to issue if client software is too old, set by p4 configure set minClientMessage=message.

Server

0

Valid values for the monitor configurable are:

• 0: Server process monitoring off. (Default)
• 1: monitor active commands
• 2: active commands and idle connections
• 3: sames as 2, but also includes connections that failed to initialize (stuck at the Init() phase)
• 5: sames as 2, but also includes a list of the files locked by the command for more than one second
• 10: same as 5, but also includes lock wait times
• 25: sames as 10, except that the list of files locked by the command includes files locked for any duration

See the p4 monitor command.

Server, Client, Proxy, Broker

TCP connection changes to improve performance over long latency connections.

To enable, set to 1. Clients set by using p4 set or P4CONFIG files. Servers set by using p4 configure. On Windows, send buffer sizes are not autotuned but manually configurable with net.tcpsize.

See the Support Knowledgebase article, "Autotune - Improved performance over long latency TCP connections".

Server, Proxy

128

Maximum length of queue for pending connections. Consider increasing if users cannot connect to servers that are heavily loaded.

Server

0

Number of unacknowledged keepalives before failure. Similar to tcp_keepalive_probes at https://linux.die.net/man/7/tcp

If 0, defaults to the operating system behavior.

See the TCP keepalive section in the Administrators Guide.

Server

0

If 0 and keepalive functionality is supported by the OS, keepalives are enabled on the socket.

If 1, keepalives are disabled on the socket.

See the TCP keepalive section in the Administrators Guide.

Server

0

Idle time (in seconds) before starting to send keepalives. Similar to tcp_keepalive_time at https://linux.die.net/man/7/tcp

If 0, defaults to the operating system behavior.

See the TCP keepalive section in the Administrators Guide.

Server

0

Interval (in seconds) between sending keepalive packets. Similar to tcp_keepalive_intvl at https://linux.die.net/man/7/tcp

If 0, defaults to the operating system behavior.

See the TCP keepalive section in the Administrators Guide.

Proxy

100

A value in megabytes that controls the proxy’s cache faulting behavior. A single p4 sync will not publish more than net.maxfaultpub megabytes of faults into pdb.lbr.

You must restart the server after changing the value of this configurable.

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 P4CONFIG file, applies to user’s workstation (and requires only that the versioning service reply to user requests within the allotted time limit).

You must restart the server after changing the value of this configurable.

Server, Proxy

1

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.

Server

Specifies the number of files in a batch.

See p4 sync on Parallel processing.

Server

512

Specifies the number of bytes in a batch.

See p4 sync on Parallel processing.

Server

0

Specifies your maximum number of threads for syncing files concurrently.

A value greater than 1 enables parallel processing up to the specified number of threads, when syncing a client or submitting files.

In addition to setting this variable, you must use the --parallel option to the p4 sync command or the p4 submit command to further describe the processing desired. If you use net.parallel.submit.* configurables to automate parallel processing, you do not need to use the --parallel option.

Values can range between 0 and 100. See the p4 sync command or the p4 submit command.

Server

9

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

576

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

8

For automatic parallel processing: specifies the number of files in a batch. (See also net.parallel.submit.batch)

Server

8

For automatic parallel processing: specifies the number of files in a batch. (See also net.parallel.submit.min)

Server

9

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 net.parallel.shelve.batch configurable.

Server

0

For automatic parallel processing: specifies the number of files in a batch.

See the p4 submit command on Parallel submits.

Server

8

For automatic parallel processing: specifies the minimum number of files to be sent in a parallel submit.

See the p4 submit command on Parallel submits.

Server

9

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 p4 submit command on Parallel submits.

Server

0

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 show command to find out how many concurrent transmit threads are executing in the server. The default value of 0 means no reduction of parallel sync threads. For this configurable to take effect, also set the monitor configurable to 1 or greater.

Server

0

Specifies your default number of threads for syncing files concurrently.

The specified threads grab work in batches.

Server

0

Set SO_REUSEPORT for listening socket.

You must restart the server after changing the value of this configurable.

Client, Server

0

If 1, permit the operating system to determine whether IPv4 or IPv6 is used when resolving hostnames. This is applicable only if a host name (either F or unqualified is used).

If an IPv4 literal address (e.g. 127.0.0.1) is used, the transport is always tcp4, and if an IPv6 literal address (e.g. ::1) is used, then the transport is always tcp6.

You must restart the server after changing the value of this configurable.

Proxy

10

Proxy

0

Server

0

Server

none

Server

0

Server

0

Server

0

Server

0

Server

0

Server

25

Server

50

Server

1000

Server

0

Server

0

Server

0

Server

0

Server

0

Server

0

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 (p4 login) is required.

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 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 and "Sync Network Estimates" for p4 sync

-v server=4 adds errors sent to the client to the server log

See also:

• "Setting server trace and tracking flags" in Helix Core Server Administrator Guide: Fundamentals

• P4LOG
• the Support Knowledgebase article, "Helix Server Trace Flags"

Server

0

Determines whether changes can be fetched.

• If set to 1, this server can fetch from other servers.
• If set to 2, other servers can fetch from this server.
• If set to 3, both 1 and 2 are allowed.

Server

0

Determines whether changes can be pushed.

• If set to 1, this server can push to other servers.
• If set to 2, other servers can push to this server.
• If set to 3, both 1 and 2 are allowed.

Server

0

DVCS configurations with files of type +l can use the --remote flag on the p4 edit, p4 delete, and p4 revert commands. This locks +l file types exclusively on the shared server. The locks are released automatically when the modified files are pushed.

The shared server must be a commit server and this configurable must have 1, not 0, as its value.

To learn about +l, see the Helix Core Server User Guide on File type modifiers.

Server

0

If set to a non-zero value, allows this server to run the p4 unsubmit and p4 fetch -u commands.

Server

0

Policy for per-command resource limits:

0: All users may use command-line overrides for MaxResults, MaxScanRows, and MaxLockTime limits defined in the p4 group specs.

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 Map: field of a depot form is evaluated. If it is not set, the Map: field relative address is evaluated with respect to the value stored in P4ROOT. For more information, see the p4 depot command.

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.global.client.views.

Server

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

Server

server.locks

Directory for server locks, specified relative to P4ROOT. To disable server locking, set this configurable to disabled. (If db.peeking is nonzero (enabled), server.locks cannot be disabled; you can disable locking by setting server.locks.sync to 0.)

Server

0

Set this configurable to 1 to make p4 lock from an edge server take global locks on the commit server by default.

Server

0

When set, the p4 sync command takes a client workspace lock in shared mode. The default value of 0 prevents sync from taking a client workspace lock.

If db.peeking is enabled, the server.locks.dir directory must exist. The changes to locking behavior that occur when you enable db.peeking obviate the need to set server.locks.dir to disabled, but if performance issues arise with respect to multiple concurrent, large, and/or interrupted p4 sync commands, you can obtain the old behavior for syncing by setting server.locks.sync to 0.

Server

0

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.

Server

none

The counter name for the structured log file designated by n. (For example, if the structured log file is errors.csv, n is 3.)

See "Logging and structured files" in the Helix Core Server Administrator Guide: Fundamentals for more information.

Server

none

Server log file name associated with each structured log file. See p4 logparse for a list of valid filenames.

n may not exceed 500.

Server

none

For each structured log file, the size, in megabytes, at which the associated log file is rotated.

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

99

Number of buckets (subdirectories) into which files in the spec depot are hashed. Set to 0 to disable hashing, which may slow performance on older filesystems where performance is a function of the number of files per directory.

Server

0

By default, Perforce’s SSL support is based on the AES256-SHA cipher suite. To use CAMELLIA256-SHA, set this tunable to 1.

ssl.tls.version.min

and

ssl.tls.version.max

Server and optionally on the client for testing

10

and

12

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 ssl.tls.version.max specifies the highest version.

Valid values are 10 for TLSv1.0, 11 for TLSv1.1, and 12 for TLSv1.2.

To see the values on the server:

p4 configure show ssl.tls.version.min
p4 configure show ssl.tls.version.max

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:

p4 configure set ssl.tls.version.min=11
p4 configure set ssl.tls.version.max=12

To allow only a single version, assign the same value to both configurables.

On a client, to verify that TLSv1.0 does not connect:

p4 -v ssl.tls.version.min=10 -v ssl.tls.version.max=10 info

Server

none

For replica servers, set startup.1 through startup.N to be p4 pull threads to be spawned at startup.

The startup.N configurables are processed sequentially. Processing stops at the first gap in the numerical sequence; any commands after a gap are ignored.

Server

state

For replica servers, the file used by the server to track the current journal position.

The default, 1, prevents submitting a changelist that contains what the server perceives as a name collision between directory name and file name. For example:

$ p4 files ...
//depot/foo/bar/myfile#1 - add change 10 (text)

$ p4 add bar
//depot/foo/bar#1 - opened for add 

$ p4 submit -d test Submitting change 11.
Locking 1 files ...
Cannot add file '//depot/foo/bar', filename collides with an existing directory path in the depot.

To remove the check, set this configurable to 0 and be aware of the risk of accidentally overwriting file content.

Server

none

Enable the generation of global changelist ids. This is relevant for users of the Helix Core Server’s distributed versioning (DVCS) features.

• uuid generates the id in uuid format.
• checksum generates the id in checksum format.
• serverid generates the id in serverid+change format.

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

0

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 --noretransfer option to the p4 submit command.

Server

0

When set, open files that users have locked (with the p4 lock command) are automatically unlocked after a failed p4 submit.

Server

10

Limit in microseconds for retrying a failed file rename. Affects Windows Rename() retry loop.

Server

none

Server

none