p4 replicate
Synopsis
Poll for journal changes on one Perforce server for forwarding to another Perforce server.
Syntax
p4 replicate [-j token
] [-s statefile
] [-i interval
] [-k -x -R] [-J prefix
]
[-T tables
] [-o output
] [command
]
Description
This command polls for new journal entries from a Perforce server, and
either outputs them to standard output, or, if a
command
is specified, pipe the journal records
to the command
, which is spawned as a
subprocess.
Options
|
Specify a journal number or position token of the form
|
|
Specify a state file which tracks the most recent journal
position. You can also use the |
|
Specify a polling interval, in seconds. The default is two
seconds. To disable polling (that is, to check once for updated
journal entries and then exit), specify an
|
|
Specifies a filename prefix for the journal, such as that used
with p4d -jc
|
|
Supply a list of database tables (for example,
|
|
Keep the pipe to the |
|
Exit the p4 replicate command when journal rotation is detected. |
|
The |
|
Specify a file for output. If a
|
|
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 |
|
-
Use p4 replicate in situations where you need to replicate metadata (but not archived files), or when you need to perform filtering operations on metadata. In most situations, replication with p4 pull is preferable to p4 replicate.
-
For more information, see Perforce Server Administrator's Guide: Multi-site Deployment and the following Perforce Knowledge Base article:
http://answers.perforce.com/articles/KB_Article/Perforce-Metadata-Replication