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.
An output format suitable for sourcing in shell scripts can be
obtained using the -s option, which ensures configuration information
is quoted and preceded by an export statement. When not reporting
the library capabilities, this mode will produce a statement that
does not override an existing setting in the environment for PCP
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 differs
greatly to the of Linux/UNIX-based operating systems.
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
firstname.lastname@example.org. 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 PMCONFIG(1)