Perform administrative operations on the server.
g-opts] admin checkpoint [-z |
g-opts] admin journal [-z]
g-opts] admin stop
g-opts] admin updatespecdepot
[-a | -s
g-opts] admin resetpassword -a |
p4 admin command allows Perforce superusers to perform
administrative tasks even when working from a different machine than the
one running the shared Perforce service.
To stop the Perforce service, use
p4 admin stop. This locks the
database to ensure that it is in a consistent state upon restart, and
then shuts down the Perforce background process.
To restart the service, use
p4 admin restart. The database is
locked, the service restarts, and any
configure settings that require a restart are then applied.
To take a checkpoint, use p4 admin checkpoint
prefix]. This is equivalent to
logging in to the server machine and taking a checkpoint with
p4d -jc [
checkpoint is taken and the journal is copied to a numbered file. If a
prefix is specified, the files are named
n is a sequence number. The MD5 checksum of the
checkpoint is written to a separate file,
lastCheckpointAction counter is updated to reflect successful
You must be connected to the server to issue the
p4 admin checkpoint
You can store checkpoints and journals in the directory of your choice
by specifying the directory as part of the prefix. (Rotated journals are
stored in the
P4ROOT directory, regardless of the directory
in which the current journal is stored.) If no prefix is specified,
the default filenames
p4 admin journal command is equivalent to
For details, see the Helix Versioning Engine Administrator Guide: Fundamentals. The files are created in the server
root specified when the Perforce service was started.
p4 admin updatespecdepot command causes the Perforce service
to archive stored forms (specifically,
job forms) into the spec
depot. If the
-a option is used, all of the form specification types
are archived. If the
-s option option is used, then only those of the
specified type are archived. Only those forms that have not yet been
archived are created.
p4 admin resetpassword command forces specified users with
existing passwords to change their passwords before they can run another
command. (This command works only for users whose
authMethod is set to
perforce. However, you can use it in a mixed environment, that is an
environment in which both Perforce-based and LDAP-based authentication
- To force password reset of all users with passwords (including the
superuser who issued the command), use
p4 admin resetpassword -a.
- To force a single users to reset their password, use
p4 admin resetpassword -u user.
p4 admin setldapusers command allows you to convert all
existing non-super users to use LDAP authentication. The command changes
AuthMethod field in the user specification for each user from
super users want to use LDAP authentication,
they must set their
See “Global Options”.
|Can File Arguments Use Revision Specifier?||Can File Arguments Use Revision Range?||Minimal Access Level Required|
p4 admin updatespecdepotand
p4 admin resetpasswordcommands require
superaccess. The others require that the user be an operator (see
p4 user) or have
To require all newly-created users with passwords to reset their passwords before invoking their first command, set the
p4 configure set dm.user.resetpassword=1
p4 admin resetpassword -aresets only the passwords of users who presently exist (and who have passwords).
p4 admin stopshuts down the Perforce service, you may see an error message indicating that the connection was closed unexpectedly. You can ignore this message.
- The spec depot must exist before running
p4 admin updatespecdepot.
p4 lockstat, and
p4 logstatare standalone commands; the old
p4 adminsyntax remains as an alias for backward compatibility.
- For more about administering Perforce, see the Helix Versioning Engine Administrator Guide: Fundamentals and Helix Versioning Engine Administrator Guide: Multi-site Deployment.
Stop the shared Perforce service
Create a checkpoint named
Create a checkpoint named