Man page of PCP.CONF
Section: Devices and Network Interfaces (4)
Return to Main Contents
pcp.conf - the Performance Co-Pilot configuration and environment file
When using Performance Co-Pilot (PCP) tools and utilities
and when calling PCP library functions, a standard set of
environment variables are defined in
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
shell script and queried by C/C++ programs using the
If a variable is already defined in the environment,
the values in
override those values, i.e. the values in
serve as installation defaults only.
files are expected to be found in
If required, the
file may be relocated and
set in the environment to specify the full path to the new location.
file can not be relocated (this is the only hard coded path
required by PCP).
The syntax rules for
are as follows :
the general syntax is
PCP_VARIABLE_NAME=variable value to end of line
lines that begin with
and all blank lines are ignored.
all variables must be prefixed with
This is a security issue - variables that do not have this prefix will
be silently ignored.
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
file may be sourced directly by Makefiles as well as interpreted by the
script and the
variable values may contain spaces and should
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
environment variable specifies an alternative path to the
- SEE ALSO
This document was created by
using the manual pages.
Time: 04:33:16 GMT, October 25, 2010