p4 monitor
Synopsis
Display Perforce process information; control long-running tasks.
Syntax
p4 [g-opts
] monitor show [-a -l -e -L [-s R/T/P/I]
p4 [g-opts
] monitor terminate id
p4 [g-opts
] monitor clear id
p4 [g-opts
] monitor clear all
p4 [g-opts
] monitor pause id
p4 [g-opts
] monitor resume id
Description
p4 monitor allows a system administrator to observe and control Perforce-related processes running on a Perforce server machine.
To use p4 monitor, you must enable monitoring on the
Perforce service by setting the monitor
configurable
with p4 configure.
You can control process monitoring by setting the
monitor
configurable to 0 (disable monitoring), 1
(enable monitoring of active processes), or 2 (enable monitoring of both
active and idle processes). Values of 5, 10, and 25 relate to obtaining
lock information.
Command syntax variants provide the following alternatives:
-
To list current process information, use p4 monitor show. By default, all processes are listed, but only the command (for example,
sync
,edit
,submit
) is shown, without arguments. This form of p4 monitor requireslist
level access. Use the-s
option to restrict the display to processes in the specified state.status
To show the list of arguments associated with each command, use the
-a
(arguments) option or-l
(long) option. For additional information from the user environment, use the-e
(environment) option. These options requireadmin
level access. Use the-L
option to show locked files. -
To mark a process for termination, use p4 monitor terminate
id
. This command requiressuper
level access.The p4 monitor terminate command will not mark a process for termination unless the process has been running for at least ten seconds. Some commands, such as p4 obliterate, cannot be terminated.
-
To remove an entry from the monitor table, use p4 monitor clear
id
. You can clear the entire table with p4 monitor clear all. Both of these commands requiresuper
level access.Processes marked as running continue to run to completion even if removed from the monitor table with p4 monitor clear.
-
To control long-running tasks such as p4 verify or p4 pull, use the p4 monitor pause and p4 monitor resume commands.
Each line of p4 monitor output consists of the following fields:
pid
status
owner
hh:mm:ss
command
[args
]
|
The process ID under Unix (or thread ID under Windows) |
|
|
|
The Perforce user name of the user who invoked the command. |
|
The time elapsed since the command was called. |
|
The command and arguments as received by the Perforce service. |
For example, consider the following output to the p4 monitor show -L command, which displays information about locked files:
8764 R user 00:00:00 edit [server.locks/clients/88,d/ws4(W),db.locks(R),db.rev(R)] 8766 R user 00:00:00 edit [server.locks/clients/89,d/ws5(W),db.locks(R),db.rev(R)] 8768 R user 00:00:00 monitor
Following pid, status, owner, and time information, this shows two edit
commands that have various files locked, including the client workspace
lock in exclusive mode for the workspaces ws4
and
ws5
, and db.locks and db.rev tables in read-only mode.
Options
|
Show all arguments associated with the process (for
example, Perforce user names are truncated to 10 characters, and each line is limited to a total of 80 characters of output. |
|
Show environment information including invoking Perforce application (if known), host IP address, and workspace name. |
|
Show all arguments in long form; that is, without truncating user names or the list of command line arguments. |
|
Show information about locked files. The information is collected only for the duration of the p4 monitor command, and is not persisted. Pre-requisites for using this option vary with the platform on which the server is running.
You can use the |
|
Restrict the display to processes in the
|
|
See “Global Options”. |
Usage Notes
Can File Arguments Use Revision Specifier? |
Can File Arguments Use Revision Range? |
Minimal Access Level Required |
---|---|---|
No |
No |
|
-
If a command terminates prematurely on the server side, it may be erroneously listed as running. Superusers can clear such processes with p4 monitor clear.
-
Some commands (for instance, p4 submit) invoke multiple processes. For example,
dm_CommitSubmit
ordm_SubmitChange
may appear in the output of p4 monitor as two separate phases of the p4 submit command. -
If you have enabled idle process monitoring (by setting the
monitor
configurable to 2), idle processes appear with astatus
ofR
, but with acommand
ofIDLE
.
Examples
p4 monitor show |
Show Perforce processes information (commands only). Requires
|
p4 monitor show -l |
Show arguments and commands, without limits on line length.
Requires |
p4 monitor show -a |
Show arguments and commands, limited to 80 characters per line
of output. Requires |
p4 monitor terminate 123 |
Instruct the Perforce service to mark process 123 for
termination. Requires |
p4 monitor clear all |
Clears the monitor table of all entries. Requires
|