Helix Core P4 Command Reference (2019.1)

Configurables - alphabetical list

The following table is an alphabetical list of the configurables. To see details about a configurable, click a letter and a name in the list.

Click a letter

ACDFJLMNPRSTZ

A

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.ldap.userautocreate
auth.sso.allow.passwd
auth.sso.args
auth.sso.allow.nonldap
auth.tickets.nounlocked

C

client.readonly.dir
client.sendq.dir

D

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.repo.noautocreate
dm.resolve.attribs
dm.rotatelogwithjnl
dm.shelve.accessupdate
dm.shelve.maxfiles
dm.shelve.maxsize
dm.shelve.promote
dm.user.accessforce
dm.user.accessupdate
dm.user.allowselfupdate
dm.user.loginattempts
dm.user.noautocreate
dm.user.resetpassword

F

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

J

journalPrefix

L

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

M

minClient
minClientMessage
monitor
monitor.lsof

N

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

P

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

R
rcs.nofsync
rejectList
rpl.checksum.auto
rpl.checksum.change
rpl.checksum.table
rpl.compress
rpl.forward.login
rpl.jnlwait.adjust
rpl.jnlwait.interval
rpl.jnlwait.max
rpl.journalcopy.location
rpl.labels.global
rpl.replay.userrp
rpl.submit.nocopy
rpl.verify.cache
run.users.authorize
S
security
server
server.allowfetch
server.allowpush
server.allowremotelocking
server.allowrewrite
server.commandlimits
server.depot.root
server.extensions.dir
server.global.client.views
server.locks.archive
server.locks.dir
server.locks.global
server.locks.sync
server.maxcommands
server.maxcommands.allow
serverlog.counter.N
serverlog.file.N
serverlog.maxmb.N
serverlog.retain.N
serviceUser
spec.hashbuckets
ssl.secondary.suite
ssl.tls.version.min
ssl.tls.version.max
startup.N
statefile
submit.allowbgtransfer
submit.autobgtransfer
submit.collision.check
submit.identity
submit.noretransfer
submit.unlocklocked
sys.rename.max
sys.rename.wait
sys.threading.groups
T
template.client
template.label
track
triggers.io
Z
zerosyncPrefix

A

Configurable Client or Server or Proxy? Default Value Meaning 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

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

No
auth.id

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.

No
auth.ldap.cafile

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.

No
auth.ldap.order.N

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.

auth.ldap.pagesize

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.

No
auth.ldap.ssllevel

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.
No
auth.ldap.timeout

Server

30

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

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: Fundamentals.

No
auth.sso.args Server unset

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%

No
auth.sso.nonldap   0
  • 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 "p4 login behavior with auth-check-sso trigger" under "Single signon and auth-check-sso triggers" in Helix Core Server Administrator Guide: Fundamentals.

No
auth.tickets.nounlocked Server 0

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

No
auth.ldap.userautocreate

Server

0

0 means no automatic creation of users.

1 means that if auth.default.method is set to ldap, users are auto-created when they log in to Perforce and they have been successfully authenticated against an active directory AD/LDAP server using p4 login.

2 is similar to 1 but also requires the user already have permissions on the server through the protections table.

No

C

Configurable Client or Server or Proxy? Default Value Meaning Server
Restart
Required?
client.readonly.dir

Server

none

The path of the directory where db.* files for a read-only client will be placed.

For example, if you create a read-only client whose name is myroc and client.readonly.dir is set to /perforce/1, then syncing files using this client will write to the database /perforce/1/server.dbs/client/hashdir/db.myroc.

No

client.sendq.dir

Server

 

none

For parallel sync: To avoid lock contention on the database table used for processing parallel syncs, set the client.sendq.dir 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

D

Configurable Client or Server or Proxy? Default Value Meaning Server
Restart
Required?
db.monitor.interval

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:

No
db.monitor.shared

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.

Note

The value is in database pages of 8 kilobytes. For example, a value of 4096 means 32 MB.

See also the Options under the p4 configure command, and note that p4 configure show indicates the actual maximum, but p4 configure show allservers indicates a manual preference that is only enforced if sufficient memory is available.

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.

db.peeking

Server

2

Enable and configure lockless reads. When enabled, many common commands no longer block other commands attempting to update the database. See "Commands implementing lockless reads" in the Helix Core Server Administrator Guide: Fundamentals .

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.

Note

Beginning with the 2017.1 release, this configurable is dynamic and no server restart is required.

db.replication

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.

No
dbjournal.bufsize

Server

16K

Buffer size for journal and checkpoint read/write operations.

No
dbopen.nofsync

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.

No
defaultChangeType

Server

none

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

No
dm.annotate.maxsize

Server

10M

Maximum revision size for p4 annotate.

No
dm.domain.accessforce

Server

3600

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

No
dm.domain.accessupdate

Server

300

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

No
dm.grep.maxrevs

Server

10K

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

No
dm.info.hide

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.

No
dm.integ.engine

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.

No
dm.keys.hide

Server

0

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

No
dm.password.minlength

Server

8

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

No
dm.protects.allow.admin

Server

0

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

No
dm.proxy.protects

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.

No
dm.repo.noautocreate

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.

No
dm.resolve.attribs

Server

1

Enable resolve for attributes set with p4 attribute.

No
dm.rotatelogwithjnl

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.

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

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

No
dm.shelve.maxfiles

Server

10M

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

No
dm.shelve.maxsize

Server

0

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

No
dm.shelve.promote

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.

No
dm.user.allowselfupdate Server 1

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

No
dm.user.accessforce

Server

3600

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

No
dm.user.accessupdate

Server

300

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

No
dm.user.loginattempts

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.

No
dm.user.noautocreate

Server

0

Control behavior of automatic user creation.

Warning

By default, Helix 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 Perforce commands cause a user to be created. You can control this behavior by setting the configurable with the p4 configure command. For greatest security, we recommend that only the Helix server superuser be allowed to create new users:

$ p4 configure set dm.user.noautocreate=2
Value Meaning

0

A user record is created whenever any new user invokes any command that updates the depot or its metadata (default). Many such commands exist, including p4 ping.

1

New users must create their own user records by explicitly running p4 user.

2

Only the Helix server superuser can create a new user, and the superuser does so by explicitly running p4 user -f username.

No
dm.user.resetpassword

Server

0

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 Password: field of the user specification. The password reset behavior for new users that get initial passwords using the p4 passwd command after the user is created is not affected by the setting of this configurable.

No

F

Configurable Client or Server or Proxy? Default Value Meaning Server
Restart
Required?
filesys.binaryscan

Client

64K

Scan the first filesys.binaryscan bytes for binary data when running p4 add.

No
filesys.bufsize

Client, Server

4K

Buffer size for client-side read/write operations.

No
filesys.checklinks

Server

0

Use to control symbolic links.

0 means no link checking, so directory symlinks can occur.

1 blocks attempts to p4 add a symlink to a directory.

  • p4 add /path/to/a/symlinkDirectory
    fails
  • p4 add /path/to/an/embeddedSymlink/readme.txt
    fails

2 same as 1 except allows the user to bypass the check by using the -f (force) option.

  • p4 add -f /path/to/a/symlinkDirectory
    succeeds
  • p4 add -f /path/to/an/embeddedSymlink/readme.txt
    succeeds

3 allows a symlink to a directory that terminates the path without having to use -f:

  • p4 add /path/to/a/symlinkDirectory
    succeeds without using
    -f because the directory that is represented by a symlink is at the end of the path
  • p4 add /path/to/an/embeddedSymlink/subdirectory/readme.txt
    fails because the directory that is represented by a symlink is NOT at the end of the path
  • p4 add -f /path/to/an/embeddedSymlink/subdirectory/readme.txt
    succeeds because -f is used
No
filesys.depot.min

Server

250M

Minimum disk space required for any depot before server rejects commands. (If there is less than filesys.depot.min disk space available for any one depot, commands are rejected for transactions involving all depots.)

To specify size, use the following binary abbreviations, which are slightly different from the more familiar decimal abbreviations:

t or T for tebibytes (1 T is approximately 1.1 TB)
g or G for gibibytes (1 G is approximately 1.07 GB)
m or M for mebibytes (1 M is approximately 1.05 MB)
k or K for kibibytes (1 K is 1,024 bytes)

You can also use a percentage to specify the relative amount of free disk space required.

No
filesys.extendlowmark

Client

32K

Minimum filesize before preallocation (Windows).

No
filesys.P4JOURNAL.min

Server

250M

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 T for tebibytes (1 T is approximately 1.1 TB)
g or G for gibibytes (1 G is approximately 1.07 GB)
m or M for mebibytes (1 M is approximately 1.05 MB)
k or K for kibibytes (1 K is 1,024 bytes)

You can also use a percentage to specify the relative amount of free disk space required.

No
filesys.P4LOG.min

Server

250M

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 T for tebibytes (1 T is approximately 1.1 TB)
g or G for gibibytes (1 G is approximately 1.07 GB)
m or M for mebibytes (1 M is approximately 1.05 MB)
k or K for kibibytes (1 K is 1,024 bytes)

You can also use a percentage to specify the relative amount of free disk space required.

No
filesys.P4ROOT.min

Server

250M

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 T for tebibytes (1 T is approximately 1.1 TB)
g or G for gibibytes (1 G is approximately 1.07 GB)
m or M for mebibytes (1 M is approximately 1.05 MB)
k or K for kibibytes (1 K is 1,024 bytes)

You can also use a percentage to specify the relative amount of free disk space required.

No
filesys.TEMP.min

Server

250M

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 T for tebibytes (1 T is approximately 1.1 TB)
g or G for gibibytes (1 G is approximately 1.07 GB)
m or M for mebibytes (1 M is approximately 1.05 MB)
k or K for kibibytes (1 K is 1,024 bytes)

You can also use a percentage to specify the relative amount of free disk space required.

No
filesys.windows.lfn

Server, Client, Proxy

1

Set to 1 to support filenames longer than 260 characters on Windows platforms.

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.

No
filetype.maxtextsize

Server

10M

Maximum file size for text type detection.

No

J

Configurable Client or Server or Proxy? Default Value Meaning Server
Restart
Required?
journalPrefix

Server

unset

Prefix or directory location for rotated journal.

No

L

Configurable Client or Server or Proxy? Default Value Meaning Server
Restart
Required?
lbr.autocompress

Server

0

Enabling this configurable specifies the storage method as compressed text (ctext) rather than RCS format text. The user still sees the file type as text.

We recommend setting this variable with p4 configure set lbr.autocompress=1 when:

  • using a commit/edge configuration
  • sharing archive files between servers
  • using pull-archive or edge-content triggers for external archive transfer
No
lbr.bufsize

Server, Proxy

4K

Buffer size for read/write operations to server’s archive of versioned files.

No
lbr.proxy.case

Proxy

1

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 Suppress on-demand file fetch No
lbr.replication

Server

unset

Control behavior of user commands that access versioned files on the Helix server server:

readonly: Replicates version files when they are updated on the master.

shared: For shared storage. (See "Configuring a replica with shared archives" in Helix Core Server Administrator Guide: Multi-Site Deployment.)

cache: Replicates version files only when referenced if they do not already exist on the replica.

none: No access to versioned files is permitted.

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

Equivalent to starting a replica p4d process with one of the -D readonly, -D shared, -D cache, or -D none options.

No
lbr.retry.max

Server

50

In the event of a failed transfer, a replica will make lbr.retry.max attempts to retrieve the file.

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.verify.in

Server

1

Verify contents from the client to server? (1 for yes, 0 for no)

No
lbr.verify.out

Client, Server

1

Verify contents from the server to client? (1 for yes, 0 for no)

No
lbr.verify.script.out

Server

1

Set to 0 to prevent files of type +X from having their digest checked when transmitted from server to client.

When source watermarking is used, sites have configured a +X archive trigger script that returns different results each time a file is sync’d or printed, in order to embed a user-specific string into the file contents during sync. This defeats the digest verification performed when sending the file to disk. Setting lbr.verify.script.out disables digest verification in this situation. Other files are still verified normally, as determined by the setting of lbr.verify.out.

No

M

Configurable Client or Server or Proxy? Default Value Meaning Server
Restart
Required?
minClient

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

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

No
minClientMessage

Server

none

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

No
monitor

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.

No
monitor.lsof

Server

none

When set on Unix platforms, enables the use of the p4 monitor command to display a list of locked files. Set to the following value:

$ path/lsof -F pln+

The value for path varies with the version of Unix you are using. For example:

$ /usr/bin/lsof -F pln

See the p4 monitor command.

No

N

Configurable Client or Server or Proxy? Default Value Meaning Server
Restart
Required?
net.autotune

Server, Client, Proxy, Broker

1

TCP connection changes to improve performance over long latency connections.

To disable, set to 0. Clients set by using p4 set or P4CONFIG files. Servers set by using p4 configure.

Note

On Windows-based platforms, send buffer sizes are not autotuned but are manually configurable with net.tcpsize.

The 2017.2, 2018.1, and 2018.2 releases defaulted to 0, for reasons explained in 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.

net.backlog

Server, Proxy

128

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

No
net.keepalive.count

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.

No
net.keepalive.disable

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.

No
net.keepalive.idle

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.

No
net.keepalive.interval

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.

No
net.maxfaultpub

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.

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.

net.maxwait

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.

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.

net.mimcheck

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.

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.

net.parallel.batch

Server

8

Specifies the number of files in a batch.

See p4 sync on Parallel processing.

No
net.parallel.batchsize

Server

512

Specifies the number of bytes in a batch.

See p4 sync on Parallel processing.

No
net.parallel.max

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.

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.

No
net.parallel.min

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.

No
net.parallel.minsize

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.

No
net.parallel.shelve.batch

Server

8

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

No
net.parallel.shelve.min

Server

8

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

No
net.parallel.shelve.threads

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.

No
net.parallel.submit.batch

Server

0

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

See the p4 submit command on Parallel submits.

No
net.parallel.submit.min

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.

No
net.parallel.submit.threads

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.

No
net.parallel.sync.svrthreads

Server

0

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

No
net.parallel.threads

Server

0

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 1, but less than or equal to the value of net.parallel.max.

See also Parallel processing.

The specified threads grab work in batches.

No
net.reuseport

Server

0

Set SO_REUSEPORT for listening socket.

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.

net.rfc3484

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.

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.

net.tcpsize

Client, Server, Proxy

512K

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)

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.

P

Configurable Client or Server or Proxy? Default Value Meaning Server
Restart
Required?
proxy.monitor.interval

Proxy

10

Set the proxy monitoring interval. Default is 10 seconds.

No
proxy.monitor.level

Proxy

0

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

None

Temporary directory for alternative archive copy.

No

push.unlocklocked

Server

0

When set, unlock locked files if p4 push fails.

No

R

Configurable Client or Server or Proxy? Default Value Meaning Server
Restart
Required?
rcs.nofsync

Server

0

Set to 1 to disable fsync() call when server writes to a versioned file in RCS format, and permit the OS to determine when to write the modified data.

No
rejectList

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.

No
rpl.checksum.auto

Server

0

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.

No
rpl.checksum.change

Server

0

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 integrity.csv if the changelist does not match.

3: Replica verifies changelist summary and writes to integrity.csv even if the changelist does match.

Setting affects p4 submit, p4 push, p4 fetch, p4 populate, and p4 unzip commands.

No
rpl.checksum.table

Server

0

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 integrity.csv if the check fails.

2: Results of journal note processing in the replica are logged even if the results match.

No
rpl.compress

Server

0

Enable replica/master network compression:

0: No data stream compression.

1: Data streams used for archive transfer to the replica (p4 pull -u) are compressed.

2: Data streams used by p4 pull -u and p4 pull are compressed.

3: All data streams (p4 pull -u, p4 pull, and data streams for commands forwarded to the master or commit server) are compressed.

4: Compress only the journal pull and journal copy connections between the replica and the master.

No
rpl.forward.login

Server

0

Set to 1 on each replica to enable single-sign-on authentication for users in a distributed configuration. The auth.id configurable must also be the same for all servers participating in a distributed configuration.

For more information, see "Authenticating users" in Helix Core Server Administrator Guide: Multi-Site Deployment.

No
rpl.jnlwait.adjust

Server

25

Used to tune server performance when a forwarding replica has lots of users. Please consult Perforce Support for guidance in adjusting values.

No
rpl.jnlwait.interval

Server

50

Used to tune server performance when a forwarding replica has lots of users. Please consult Perforce Support for guidance in adjusting values.

No
rpl.jnlwait.max

Server

1000

Used to tune server performance when a forwarding replica has lots of users. Please consult Perforce Support for guidance in adjusting values.

No
rpl.journalcopy.location

Server

0

Set to 0 means that the journalcopy thread writes the journal directly to the filepath with a prefix of the standby server's journalPrefix.

Set to 1 means that the journalcopy thread writes the journal to where the standby server's P4JOURNAL would be written. The journal is then rotated to the filepath with a prefix of the standby server's journalPrefix.

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

0

A multi-site deployment supports both local and global labels. See "Introduction to federated services" in Helix Core Server Administrator Guide: Multi-Site Deployment.

0 means local is the default 1 changes default to global
a local label is restricted to the single edge server on which it is created and updated, and cannot be used on other servers a global label is created and updated on the commit server, and visible to all servers
The -g option of p4 label, p4 labelsync, and p4 tag specifies whether the label being applied is local to an edge server, or globally available from the commit server:

To create or update a global label on an edge server, use the -g option. For example,

p4 label -g myGlobalLabel

The command

p4 configure set rpl.labels.global=1

means that any new label will be global.

Existing local labels remain local. To update a local label, use the -g option.

To convert a local label into a global label, use p4 unload, then p4 reload to load the label onto the commit server.

No
rpl.replay.userrp

Server

0

To replicate the db.user.rp table, set to 1 .

The db.user.rp table contains information about users who have directly logged into and used a replica. It records the ticket that the replica issued to the user and the last time the user accessed the replica. This table is currently journaled, but it is not replicated by default.

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 db.user.rp table. This would disable the automatic filtering of db.user.rp records, and your replica would then replay (and re-journal) all the db.user.rp journal records it receives from its target.

No
rpl.submit.nocopy

Server

0

Disable default submit archive file copy

No
rpl.verify.cache

Server

0

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
run.users.authorize

Server

0

If set to 1, requires a user to authenticate before running p4 users.

No

S

Configurable Client or Server or Proxy? Default Value Meaning Server
Restart
Required?
security

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.

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 to the server log

See also:

No
server.allowfetch

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.
No
server.allowpush

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.
No
server.allowremotelocking

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.

No
server.allowrewrite

Server

0

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

No
server.commandlimits

Server

0

Policy for per-command resource limits:

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

1: Per-command options can specify lower, but not higher, resource limits.

2: All command-line resource limit options are silently ignored.

No
server.depot.root

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.

No
server.extensions.dir Server   Directory for Extension-owned storage No
server.global.client.views

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.

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

No
server.locks.dir

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

No
server.locks.global

Server

0

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

No
server.locks.sync

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.

No
server.maxcommands

Server

0

If monitoring is enabled, and if this configurable is set to a nonzero value, and the limit is exceeded:

  • Helix Core server refuses to accept more than this many simultaneous command requests
  • users receive the TooManyCommands error

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

See also server.maxcommands.allow.

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.maxcommands.allow Server 1

Allow super and operator users access to a subset of commands even if server.maxcommands is reached. For the list of these commands, see "Limiting simultaneous connections" in the Helix Core Server Administrator Guide: Fundamentals.

To disable, set to 0.

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.

serverlog.counter.N

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.

No
serverlog.file.N

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.

No
serverlog.maxmb.N

Server

none

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

No
serverlog.retain.n

Server

none

For each structured log file, the number of rotated log files to retain on the server at any one time.

No
serviceUser

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.

No
spec.hashbuckets

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.

No
ssl.secondary.suite

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.

No

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

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.

startup.N

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.

No
statefile

Server

state

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

No
submit.allowbgtransfer Server 0

To enable background archive transfer, set to 1 on ALL the servers that participate in your replicated environment.

See:

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.

submit.autobgtransfer Server 0

Assuming you have set submit.allowbgtransfer on ALL the servers that participate in your replicated environment, to make p4 submit function as if it were an alias for p4 submit -b on one or more servers, set to 1 on those servers.

See "Background archive transfer for edge server submits" in Helix Core Server Administrator Guide: Multi-Site Deployment.

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.

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

No
submit.identity

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.

No
submit.noretransfer

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.

No
submit.unlocklocked

Server

0

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

No
sys.rename.max

Server and client

10

Limit the number to retries to rename a file if renaming fails. Affects Windows Rename() retry loop. Set on the server and each client.

No
sys.rename.wait

Server and client

1000

Timeout in microseconds between file rename attempts. Affects Windows Rename() retry loop. Set on the server and each client.

No
sys.threading.groups Server 0 If set to 1, adds support for utilizing multiple processor groups on Windows Server 2008 R2 or later. After you change the value of this configurable, you must explicitly "stop" the server. 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.

T

Configurable Client or Server or Proxy? Default Value Meaning Server
Restart
Required?
template.client

Server

none

Specifies the default client to be used as a template if the user omits the -t option on the p4 client command.

No
template.label

Server

none

Specifies the default label to be used as a template if the user omits the -t option on the p4 label command.

No
track Server   Set by the server. See "Performance Tracking" in Helix Core Server Administrator Guide: Fundamentals. No
triggers.io

Server

0

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

Z

Configurable Client or Server or Proxy? Default Value Meaning Server
Restart
Required?
zerosyncPrefix

Server

none

If set, changes default behavior of p4 sync such that if a client workspace begins with this prefix, all sync operations to affected workspaces assume p4 sync -k, and do not alter contents of the workspace.

No