PMPOST(1) General Commands Manual PMPOST(1)NAME
pmpost - append messages to the Performance Co-Pilot notice board
SYNOPSIS
$PCP_BINADM_DIR/pmpost message
DESCRIPTION
pmpost will append the text message to the end of the Performance Co-Pilot (PCP) notice board file ($PCP_LOG_DIR/NOTICES) in an atomic man-
ner that guards against corruption of the notice board file by concurrent invocations of pmpost.
The PCP notice board is intended to be a persistent store and clearing house for important messages relating to the operation of the PCP
and the notification of performance alerts from pmie(1) when other notification options are either unavailable or unsuitable.
Before being written, messages are prefixed by the current time, and when the current day is different to the last time the notice board
file was written, pmpost will prepend the message with the full date.
If the notice board file does not exist, pmpost will create it. pmpost would usually run from long-running PCP daemons executing under the
(typically unprivileged) $PCP_USER and $PCP_GROUP accounts. The file should be owned by root, and group writable by the $PCP_GROUP group.
FILES
$PCP_LOG_DIR/NOTICES
the PCP notice board file
PCP ENVIRONMENT
The file /etc/pcp.conf contains the local values for PCP_ variables.
UNIX SEE ALSO logger(1).
WINDOWS SEE ALSO pcp-eventlog(1).
SEE ALSO pmie(1), pcp.conf(5) and pcp.env(5).
Performance Co-Pilot PCP PMPOST(1)
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)