pmconfig(1) [centos man page]

PMCONFIG(1)						      General Commands Manual						       PMCONFIG(1)

NAME

       pmconfig - Performance Co-Pilot configuration parameters

SYNOPSIS

       $PCP_BINADM_DIR/pmconfig [-a|-l] [-L] [-s] [name ...]

DESCRIPTION

       pmconfig displays the values for some or all configuration parameters of the local Performance Co-Pilot toolkit installation.

       The  -L	option	may be used to change the default reporting mode so that the capabilities of the PCP library are reported, rather than the
       PCP environment.

       In the default operating mode, pmconfig is often used in conjunction with the $PCP_DIR environment variable to setup scripts running  under
       the Windows operating system, where the filesystem hierarchy is very different to the of Linux/UNIX-based operating systems.

PCP ENVIRONMENT

       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	configura-
       tion file, as described in pcp.conf(5).

SEE ALSO

       pmGetConfig(3), pcp.conf(5) and pcp.env(5).

Performance Co-Pilot							PCP							       PMCONFIG(1)

PMSIGNAL(1)						      General Commands Manual						       PMSIGNAL(1)

NAME

       pmsignal - send a signal to one or more processes

SYNOPSIS

       $PCP_BINADM_DIR/pmsignal [-a|-l] [-n] [-s signal] [PID ...|name ...]

DESCRIPTION

       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 using PID or the
       binary name (with -a option).

       If a signal is not specified, then the TERM signal will be sent.

       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.

PCP ENVIRONMENT

       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 configura-
       tion file, as described in pcp.conf(5).

SEE ALSO

       kill(1), killall(1), pcp.conf(5) and pcp.env(5).

Performance Co-Pilot							PCP							       PMSIGNAL(1)