The pcp.env script is sourced by assorted Performance Co-Pilot (PCP)
scripts and utilities to define the PCP operating environment
variables. The conjugate for executable programs using the PCP
libraries is the __pmGetConfig(3) function.
Typical usage of pcp.env in a script is as follows :
# source the PCP environment variables
rest of script ...
The full syntax and semantics of the pcp.conf file and the
__pmGetConfig function are described in their respective reference
If the file $HOME/.pcp/pcp.conf exists then this will be processed
after the system-wide pcp.conf file. This provides a mechanism to
selectively modify or augment the environment settings for PCP
scripts, which maybe useful if the scripts are run with sudo(1) which
cleans the environment of important settings that are required to
ensure the correct execution of the PCP scripts, e.g. $PATH or
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 PCP.ENV(5)