p4 replicate
Poll for journal changes on one P4 Server for forwarding to another P4 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
      P4 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 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
	       | 
| 
 | Specify a journal number or position token of the form
	       | 
| 
 | Specifies a filename prefix for the journal, such as that used
	      with  | 
| 
 | Keep the pipe to the  | 
| 
 | Specify a file for output. If a  | 
| 
 | The  | 
| 
 | Specify a state file which tracks the most recent journal
	      position. You can also use the  | 
| 
 | Supply a list of database tables (for example,
	       | 
| 
 | Exit the  | 
| 
 | See Global options. | 
Usage notes
| Can File Arguments Use Revision Specifier? | Can File Arguments Use Revision Range? | Minimal Access Level Required | 
|---|---|---|
| N/A | N/A | 
 | 
- Use p4 replicatein 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 withp4 pullis preferable top4 replicate.
- 
                                                    See Replication in the P4 Server Administration Documentation. 
Related commands
| To update file content as well as journal records | |
| To display journal or checkpoint records in raw form |