Perforce 2002.2 Command Reference | ||
<< Previous Chapter p4 add |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 annotate |
To stop the server, use p4 admin stop. This locks the database to ensure that it is in a consistent state upon server restart, and then shuts down the Perforce background process. (For Windows users, this works 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 is taken and the journal is copied to a numbered file. If a prefix is specified, the files are 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 are used. Use the -z option to save the checkpoint and journal files in compressed form.
The files are created in the server root specified when the Perforce server was started.
-z |
For p4 admin checkpoint, save the checkpoint and saved journal file in compressed (gzip) format, appending the .gz suffix to the files. |
See the Global Options section. |
Perforce 2002.2 Command Reference | ||
<< Previous Chapter p4 add |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 annotate |