1PCP(1)                      General Commands Manual                     PCP(1)
2
3
4

NAME

6       pcp - summarize a Performance Co-Pilot (PCP) installation
7

SYNOPSIS

9       pcp [-p] [-a archive] [-h host] [-n pmnsfile] [host]
10

DESCRIPTION

12       The  pcp  command summarizes the status of a Performance Co-Pilot (PCP)
13       installation.  The report includes: the OS version, a  summary  of  the
14       hardware  inventory, the local timezone, details of valid PCP licenses,
15       the PCP software version, the state of the pmcd(1) process and  associ‐
16       ated  Performance Metrics Domain Agents (PMDAs), as well as information
17       about any PCP archive loggers (pmlogger(1)) and PCP  inference  engines
18       (pmie(1)) that are running.
19
20       For more general information about PCP, refer to PCPIntro(1).
21
22       With no arguments, pcp reports on the local host, however the following
23       options are accepted:
24
25       -a archive
26              Report the PCP configuration as described in the PCP archive log
27              archive.
28
29       -h host
30              Report the PCP configuration on host rather than the localhost.
31
32       -n pmnsfile
33              Load  an  alternative  Performance  Metrics Name Space (pmns(4))
34              from the file pmnsfile.
35
36       -p     Display pmie performance information - counts of rules  evaluat‐
37              ing  to  true,  false, or indeterminate, as well as the expected
38              rate of rule calculation, for each pmie process running  on  the
39              default host.  Refer to the individual metric help text for full
40              details on these values.
41
42       All of the displayed values are performance metric values  and  further
43       information for each can be obtained using the command:
44
45          $ pminfo -dtT metric
46
47       The  complete  set  of metrics required by pcp to produce its output is
48       contained in $PCP_VAR_DIR/config/pmlogger/config.pcp.
49
50       When displaying running pmlogger instances, as a  space-saving  measure
51       pcp  will  display a relative path to the archive being created if that
52       archive is located below a  pcplog  subdirectory,  otherwise  the  full
53       pathname  is  displayed  (the  PCP  log  rotation and periodic pmlogger
54       checking  facilities   support   the   creation   of   archives   below
55       $PCP_LOG_DIR/pmlogger/<hostname>).
56
57       A  similar  convention  is  used for trimming the amount of information
58       displayed for running pmie instances, where configuration  files  below
59       $PCP_VAR_DIR/config will be displayed in truncated form.
60

FILES

62       $PCP_VAR_DIR/config/pmlogger/config.pcp
63                 pmlogger configuration file for collecting all of the metrics
64                 required by pcp.
65

PCP ENVIRONMENT

67       Environment variables with the prefix PCP_ are used to parameterize the
68       file  and  directory names used by PCP.  On each installation, the file
69       /etc/pcp.conf contains the  local  values  for  these  variables.   The
70       $PCP_CONF  variable may be used to specify an alternative configuration
71       file, as described in pcp.conf(4).
72

SEE ALSO

74       PCPIntro(1), pmcd(1), pmie(1), pmlogger(1), pcp.conf(4) and pcp.env(4).
75

DIAGNOSTICS

77       pcp will terminate with an exit status of 1 if pmcd on the target  host
78       could  not  be reached or the archive could not be opened, or 2 for any
79       other error.
80
81
82
83Performance Co-Pilot                  SGI                               PCP(1)
Impressum