p4 admin

Synopsis

Syntax

Description

To stop the server, use p4 admin stop. This will lock the database to ensure that it is in a consistent state upon server restart, and then shut down the Perforce background process. (For NT users, this will work whether you are running Perforce as a server or a service.)

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 [prefix.] A checkpoint will be taken and the journal will be copied to a numbered file. If a prefix is specified, the files will be named prefix.ckp.n or prefix.jnl.n respectively, where n is a sequence number. If no prefix is specified, the default filenames checkpoint.n and journal.n will be used. Use the -z option to save the checkpoint and journal files in compressed form.

The files will be created in the server root as specified when the Perforce server was started.

Options

-z	For p4 admin checkpoint, save the checkpoint and saved journal file in compressed (gzip) format, appending the .gz suffix to the files.
g_opts	See the Global Options section.

Usage Notes

Can File Arguments Use Revision Specifier?	Can File Arguments Use Revision Range?	Minimal Access Level Required
N/A	N/A	super

• Because p4 admin stop shuts down the Perforce server, you may see an error message indicating that the connection between the client and server was closed unexpectedly. This message can be ignored.

• For more about administering Perforce, see the Perforce System Administrator's Guide.

Examples

p4 admin stop	Stop the Perforce server
p4 admin checkpoint	Create a checkpoint named checkpoint.n, and start a new journal named journal, copying the old journal file to journal.n, where n is a sequence number.
p4 admin checkpoint foo	Create a checkpoint named foo.ckp.n, and start a new journal named journal, copying the old journal file to foo.jnl.n, where n is a sequence number.