Open topic with navigation
Set and manage server configuration variables.
p4 [g-opts] configure set [P4NAME#|server_id#]variable=value
p4 [g-opts] configure unset [P4NAME#|server_id#]variable
p4 [g-opts] configure show [allservers | P4NAME | variable]
Configuration variables are used to control and customize the behavior of the Perforce service.
The configuration variables are described in:
p4 help configurables
p4 help environment,
Configurable settings might affect the client, the server, or a proxy.
p4 configure command provides one way to change
the configuration of an active server. For information on how you set
configurables that affect the client or the proxy, see
You can set configurables in the following ways for the server; methods are shown in order of precedence:
As command line options that are passed at server startup. For example:
$ p4d -v net.keepalive.idle=2700
Persistently, using the
p4 configure set
This method allows you to set the specified configurable for a named server or for any server.
Using environment variables.
p4 configure show to display the configuration
state of the current server, a named server, or any configurable. Each
configurable is displayed along with its value and an indication of what
method was used to set it. Use
p4 configure unset to
unset the value of a configurable.
Perforce, it is
good practice to enable process monitoring by setting
monitor to 1 or 2, require ticket-based authentication by
security to 3 or 4, and preventing the automatic
creation of new users by setting
dm.user.noautocreate to 1
or 2. Setting
dm.user.resetpassword to 1 is also advisable;
new users that you create (and to whom you assign an initial password)
are forced to reset their passwords before they can issue commands.
Changes to dynamic configurables take effect the next time the server receives a new connection. Changes to static configurables, require a server restart. Values of read-only configurables may not be changed.
Changes to most configurables take effect immediately; for example, you
do not have to restart the service in order for changes to configurables
monitor (enable/disable the
p4 monitor command) or
security (set the security level) to take effect.
startup. configurables used in
net.backlog require a restart.
To restart the server, use
p4 admin restart.
Servers can be identified by name. In replicated and distributed
environments, a master can control the settings of multiple replicas by
specifying the server name as part of the configurable. For example, the
following command sets the value of the
configurable for an edge server (
tokyo_edge). The command is
executed on the commit server.
$ p4 set tokyo_edge#serviceUser=svc_tokyo_edge
See Helix Versioning Engine Administrator Guide: Multi-Site Deployment for details.
server is not running or you cannot access the server, you can use the
p4d command to list, set, and unset server
To list all server configuration variables, use the
-cshow option. For example:
$ p4d -r $P4ROOT -cshow
To set or unset values, use
-cunset. For example:
$ p4d -r $P4ROOT "-cset myServer#auth.ldap.timeout=30" $ p4d -r $P4ROOT "-cunset myServer#db.replication"
For more information, see Accessing Server Configuration Variables:
Sets the named variable to the provided value.
Unsets the named variable.
Shows the current configuration of the server currently
Regarding the maximum size of
Shows the configuration variables for all servers known to the system.
Shows the setting of a specific configuration variable.
server was invoked with
See Global Options.
|Can File Arguments Use Revision Specifier?||Can File Arguments Use Revision Range?||Minimal Access Level Required|
To list all counters and their values