pmsignal provides a cross-platform event signalling mechanism for use
with tools from the Performance Co-Pilot toolkit. It can be used to
send a named signal (only HUP, USR1, TERM, and KILL are accepted) to
one or more processes.
The processes are specified directly using PIDs or as program names
(with either the -a/--all or -p/--program options). In the all case,
the set of all running processes is searched for a basename(1) match
on name. In the program case, process identifiers are extracted from
files in the $PCP_RUN_DIR directrory where file names are matched on
The -n/--dry-run option reports the list of process identifiers that
would have been signalled, but no signals are actually sent.
If a signal is not specified, then the TERM signal will be sent. The
list of supported signals is reported when using the -l/--list
On Linux and UNIX platforms, pmsignal is a simple wrapper around the
kill(1) command. On Windows, the is no direct equivalent to this
mechanism, and so an alternate mechanism has been implemented - this
is only honoured by PCP tools, however, not all Windows utilities.
Environment variables with the prefix PCP_ are used to parameterize
the file and directory names used by PCP. On each installation, the
file /etc/pcp.conf contains the local values for these variables.
The $PCP_CONF variable may be used to specify an alternative
configuration file, as described in pcp.conf(5).
This page is part of the PCP (Performance Co-Pilot) project.
Information about the project can be found at ⟨http://www.pcp.io/⟩.
If you have a bug report for this manual page, send it to
email@example.com. This page was obtained from the project's upstream
Git repository ⟨git://git.pcp.io/pcp⟩ on 2017-03-13. If you discover
any rendering problems in this HTML version of the page, or you
believe there is a better or more up-to-date source for the page, or
you have corrections or improvements to the information in this
COLOPHON (which is not part of the original manual page), send a mail
Performance Co-Pilot PCP PMSIGNAL(1)