1PMSIGNAL(1) General Commands Manual PMSIGNAL(1)
2
6 pmsignal - send a signal to one or more processes
7
9 $PCP_BINADM_DIR/pmsignal [-alnp] [-s signal] [PID ...|name ...]
10
12 pmsignal provides a cross-platform event signalling mechanism for use
13 with tools from the Performance Co-Pilot toolkit. It can be used to
14 send a named signal (only HUP, USR1, TERM, and KILL are accepted) to
15 one or more processes.
16 The processes are specified directly using PIDs or as program names
18 (with either the -a/--all or -p/--program options). In the all case,
19 the set of all running processes is searched for a basename(1) match on
20 name. In the program case, process identifiers are extracted from
21 files in the $PCP_RUN_DIR directrory where file names are matched on
22 name.pid.
23 The -n/--dry-run option reports the list of process identifiers that
25 would have been signalled, but no signals are actually sent.
26 If a signal is not specified, then the TERM signal will be sent. The
28 list of supported signals is reported when using the -l/--list option.
29 On Linux and UNIX platforms, pmsignal is a simple wrapper around the
31 kill(1) command. On Windows, the is no direct equivalent to this mech‐
32 anism, and so an alternate mechanism has been implemented - this is
33 only honoured by PCP tools, however, not all Windows utilities.
34
36 Environment variables with the prefix PCP_ are used to parameterize the
37 file and directory names used by PCP. On each installation, the file
38 /etc/pcp.conf contains the local values for these variables. The
39 $PCP_CONF variable may be used to specify an alternative configuration
40 file, as described in pcp.conf(5).
41
43 basename(1), kill(1), killall(1), pcp.conf(5) and pcp.env(5).
44Performance Co-Pilot PCP PMSIGNAL(1)