PCP.CONF(5) File Formats Manual PCP.CONF(5)NAME
pcp.conf - the Performance Co-Pilot configuration and environment file
SYNOPSIS
/etc/pcp.conf
DESCRIPTION
When using Performance Co-Pilot (PCP) tools and utilities and when calling PCP library functions, a standard set of environment variables
are defined in /etc/pcp.conf. These variables are generally used to specify the location of various PCP pieces in the file system and may
be loaded into shell scripts by sourcing the /etc/pcp.env(5) shell script and queried by C/C++ programs using the pmGetConfig(3) library
function. If a variable is already defined in the environment, the values in pcp.conf do not override those values, i.e. the values in
pcp.conf serve as installation defaults only.
Both the pcp.env and pcp.conf files are expected to be found in /etc by default. If required, the pcp.conf file may be relocated and
PCP_CONF set in the environment to specify the full path to the new location. The pcp.env file can not be relocated (this is the only hard
coded path required by PCP).
The syntax rules for pcp.conf are as follows :
1. the general syntax is
PCP_VARIABLE_NAME=variable value to end of line
2. lines that begin with # and all blank lines are ignored.
3. all variables must be prefixed with PCP_. This is a security issue - variables that do not have this prefix will be silently ignored.
4. there should be no space between the variable name and the literal = and no space between the = and the variable value (unless the
value actually starts with a space). This is required because the pcp.conf file may be sourced directly by Makefiles as well as inter-
preted by the pcp.env script and the pmGetConfig function.
5. variable values may contain spaces and should not be quoted. The pcp.env script automatically quotes all variable values from the
character immediately following the = through to the end of the line.
For further details and an explanation of the use of each variable, see the comments in the /etc/pcp.conf file itself.
ENVIRONMENT
The PCP_CONF environment variable specifies an alternative path to the pcp.conf file.
SEE ALSO PCPIntro(1), PCPIntro(3), PMAPI(3), pmGetConfig(3) and pcp.env(5).
Performance Co-Pilot PCP PCP.CONF(5)
Check Out this Related Man Page
PCP(1) General Commands Manual PCP(1)NAME
pcp - summarize a Performance Co-Pilot (PCP) installation
SYNOPSIS
pcp [-p] [-a archive] [-h host] [-n pmnsfile]
DESCRIPTION
The pcp command summarizes the status of a Performance Co-Pilot (PCP) installation. The report includes: the OS version, a summary of the
hardware inventory, the local timezone, details of valid PCP licenses, the PCP software version, the state of the pmcd(1) process and asso-
ciated Performance Metrics Domain Agents (PMDAs), as well as information about any PCP archive loggers (pmlogger(1)) and PCP inference
engines (pmie(1)) that are running.
For more general information about PCP, refer to PCPIntro(1).
With no arguments, pcp reports on the local host, however the following options are accepted:
-a archive
Report the PCP configuration as described in the PCP archive log archive.
-h host
Report the PCP configuration on host rather than the local host.
-n pmnsfile
Load an alternative Performance Metrics Name Space (pmns(5)) from the file pmnsfile.
-p Display pmie performance information - counts of rules evaluating to true, false, or indeterminate, as well as the expected rate of
rule calculation, for each pmie process running on the default host. Refer to the individual metric help text for full details on
these values.
All of the displayed values are performance metric values and further information for each can be obtained using the command:
$ pminfo -dtT metric
The complete set of metrics required by pcp to produce its output is contained in $PCP_SYSCONF_DIR/pmlogger/config.pcp.
When displaying running pmlogger instances, as a space-saving measure pcp will display a relative path to the archive being created if that
archive is located below a pcplog subdirectory, otherwise the full pathname is displayed (the PCP log rotation and periodic pmlogger check-
ing facilities support the creation of archives below $PCP_LOG_DIR/pmlogger/<hostname>).
A similar convention is used for trimming the amount of information displayed for running pmie instances, where configuration files below
$PCP_VAR_DIR/config will be displayed in truncated form.
FILES
$PCP_SYSCONF_DIR/pmlogger/config.pcp
pmlogger configuration file for collecting all of the metrics required by pcp.
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 PCPIntro(1), pmcd(1), pmie(1), pmlogger(1), pcp.conf(5) and pcp.env(5).
DIAGNOSTICS
pcp will terminate with an exit status of 1 if pmcd on the target host could not be reached or the archive could not be opened, or 2 for
any other error.
Performance Co-Pilot PCP PCP(1)