1PMSIGNAL(1)                 General Commands Manual                PMSIGNAL(1)
2
3
4

NAME

6       pmsignal - send a signal to one or more processes
7

SYNOPSIS

9       $PCP_BINADM_DIR/pmsignal [-alnp] [-s signal] [PID ...|name ...]
10

DESCRIPTION

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
17       The processes are specified directly using PIDs  or  as  program  names
18       (with  either  the  -a or -p options).  In the all case, the set of all
19       running processes is searched for a basename(1) match on name.  In  the
20       program  case,  process  identifiers  are  extracted  from files in the
21       $PCP_RUN_DIR directrory where file names are matched on name.pid.
22
23       The -n option reports the list of process identifiers that  would  have
24       been signalled, but no signals are actually sent.
25
26       If  a  signal is not specified, then the TERM signal will be sent.  The
27       list of supported signals is reported when using the -l option.
28
29       On Linux and UNIX platforms, pmsignal is a simple  wrapper  around  the
30       kill(1) command.  On Windows, the is no direct equivalent to this mech‐
31       anism, and so an alternate mechanism has been  implemented  -  this  is
32       only honoured by PCP tools, however, not all Windows utilities.
33

OPTIONS

35       The available command line options are:
36
37       -a, --all
38            Send signal to all named processes.
39
40       -l, --list
41            List supported signals.
42
43       -n, --dry-run
44            List processes that would be affected.
45
46       -p, --program
47            Extract programs from PCP runtime PID files.
48
49       -s signal, --signal=signal
50            Specify the signal to send, one of: HUP, USR1, TERM, KILL.
51
52       -?, --help
53            Display usage message and exit.
54

PCP ENVIRONMENT

56       Environment variables with the prefix PCP_ are used to parameterize the
57       file and directory names used by PCP.  On each installation,  the  file
58       /etc/pcp.conf  contains  the  local  values  for  these variables.  The
59       $PCP_CONF variable may be used to specify an alternative  configuration
60       file, as described in pcp.conf(5).
61

SEE ALSO

63       basename(1), kill(1), killall(1), pcp.conf(5) and pcp.env(5).
64
65
66
67Performance Co-Pilot                  PCP                          PMSIGNAL(1)
Impressum