NAME¶

pmdbg - report Performance Co-Pilot debug options

SYNOPSIS¶

pmdbg [-l]

DESCRIPTION¶

The components of the Performance Co-Pilot (PCP) use a global mechanism to control diagnostic and debug output.

pmdbg prints out all the available debug options with the name of the option and some descriptive text.

The -l option does nothing, but is included for backwards compatibility with older versions of pmdbg.

Most applications using the facilities of the PCP support a -D name[,name ...] command-line syntax to enable debug control using the name(s) of the desired debug options.

Alternatively the initial value of the debug control flags may be set to a comma-separated list if option name(s) using the environment variable $PCP_DEBUG, provided the applications use pmGetOptions(3) to process command line options and arguments. If both mechanisms are used the effect is additive, so the resultant flags are those set via $PCP_DEBUG combined with those set via any -D command line options.

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

COMPATIBILITY¶

Prior to PCP 7.0 debug options were maintained in a dual state with an old-style binary encoded integer (plus macro name for programmers), and a new-style character string name for each debug option.

In PCP 7.0 support for the the old-style was dropped.

The table below documents the equivalence for those debugging options that appeared in both the the old and the new styles.

SEE ALSO¶

PCPIntro(1), PMAPI(3), pmClearDebug(3), pmGetDebug(3), pmGetOptions(3), pmSetDebug(3), pcp.conf(5) and pcp.env(5).