mkaf(1) [centos man page]
MKAF(1) General Commands Manual MKAF(1) NAME
mkaf - create a Performance Co-Pilot archive folio SYNOPSIS
$PCP_BINADM_DIR/mkaf [findopts] filename ... DESCRIPTION
A collection of one or more Performance Co-Pilot (see PCPIntro(1)) archive logs may be combined with mkaf to produce a PCP archive folio and the associated archive folio control file. Some PCP tools use mkaf to create archive folios, e.g. the ``record'' facility in the pmchart(1) and pmview(1) tools, to facilitate playback with pmafm(1). mkaf processes each filename argument, and if this is a component file from a PCP archive that archive is added to the folio. If filename is a directory, then this is searched recursively using find(1). Any filename argument beginning with a ``-'' is assumed to be a find(1) command line option (findopts); the default is -follow if no findopts are specified. The first named archive in the folio is assumed to be associated with the default host for any tool that tries to replay multiple archives from the folio. The folio control file is written to standard output, and has the following format. 1. The first line contains the word PCPFolio. 2. The second line contains the tag Version: followed by the format version number (currently 1). 3. For subsequent lines, blank lines and lines beginning with ``#'' are ignored. 4. The line beginning with the tag Created: documents where and when the folio was created. 5. The line beginning with the tag Creator: identifies the tool which created the folio (and is assumed to know how to replay the archive folio). If present, the second argument is the name of a configuration file that the creator tool could use to replay the archive folio, e.g. with the replay command for pmafm(1). In the case of mkaf (unlike pmchart(1) or pmview(1)) there is no knowledge of the contents of the archives, so the ``creator'' cannot replay the archive, however pmchart(1) is able to replay any archive, and so this tool is identified as the Creator: for archive folios created by mkaf(1). 6. This is then followed by one or more lines beginning with the tag Archive: followed by the hostname and base name of the archive. For example $ mkaf mydir/gonzo might produce the following folio control file. PCPFolio Version: 1 # use pmafm(1) to process this PCP archive folio # Created: on gonzo at Tue Jul 2 03:35:54 EST 1996 Creator: pmchart # Host Basename # Archive: gonzo mydir/gonzo/960627 Archive: gonzo mydir/gonzo/960628 Archive: gonzo mydir/gonzo/960629 Archive: gonzo mydir/gonzo/960630 Archive: gonzo mydir/gonzo/960701 Archive: gonzo mydir/gonzo/960701.00.10 Archive: gonzo mydir/gonzo/960701.05.25 Archive: gonzo mydir/gonzo/960702.00.10 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
find(1), PCPIntro(1), pmafm(1), pmchart(1), pmview(1), pcp.conf(5) and pcp.env(5). DIAGNOSTICS
Some informational messages, warnings and pathological conditions are reported on standard error. Performance Co-Pilot PCP MKAF(1)
Check Out this Related Man Page
PMCLIENT(1) General Commands Manual PMCLIENT(1) NAME
pmclient - a simple performance metrics client SYNOPSIS
pmclient [-a archive] [-h host] [-n pmnsfile] [-p] [-S numsec] [-s samples] [-t interval] [-Z timezone] [-z] DESCRIPTION
pmclient is a simple client that uses the Performance Metrics Application Programming Interface (PMAPI) to report some high-level system performance metrics. The real value of pmclient is as a sample client using the PMAPI(3), interfaces and to this end the source code is included with the Per- formance Co-Pilot (PCP) package (see PCPIntro(1)), and is typically installed in /usr/share/pcp/demos/pmclient. Normally pmclient operates on the distributed Performance Metrics Name Space (PMNS), however if the -n option is specified an alternative local PMNS is loaded from the file pmnsfile. Unless directed to another host by the -h option, or to an archive by the -a option, pmclient will contact the Performance Metrics Collec- tor Daemon (PMCD) on the local host to obtain the required information. The -a and -h options are mutually exclusive. By default, pmclient reports the time of day according to the local timezone on the system where pmclient is run. The -Z option changes the timezone to timezone in the format of the environment variable TZ as described in environ(5). The -z option changes the timezone to the local timezone at the host that is the source of the performance metrics, as identified via either the -h or -a options. Other options control the specific information to be reported. -p The default behavior for replaying an archive, is to replay at full speed. The -p option may be used in conjunction with an ar- chive, to request that the prevailing real-time delay be applied between samples (see -t) to effect a pause. -S numsec The -S option may be used in conjunction with an archive to request that display start at the time numsec seconds from the start of the archive. -s samples The argument samples defines the number of samples to be retrieved and reported. If samples is 0 or -s is not specified, pmclient will sample and report continuously (in real time mode) or until the end of the PCP archive (in archive mode). -t interval The default update interval may be set to something other than the default 5 seconds. The interval argument follows the syntax described in PCPIntro(1), and in the simplest form may be an unsigned integer (the implied units in this case are seconds). The output from pmclient is directed to standard output, and lists + Aggregate CPU utilization, in the range 0 to 1. + If the system has more than 1 CPU, the ordinal number of the busiest CPU, in the range 0 to ... + If the system has more than 1 CPU, the CPU utilization for the busiest CPU. + Real free memory in Mbytes. + Aggregate physical disk I/O operations per second (IOPS). + Load average over the last 1 minute and over the last 15 minutes. FILES
$PCP_VAR_DIR/pmns/* default PMNS specification files $PCP_DEMOS_DIR/pmclient source code and Makefiles when pcp.sw.demo is installed $PCP_SYSCONF_DIR/pmlogger/config.pmclient pmlogger(1) configuration for creating an archive suitable for replay with pmclient 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), pmchart(1), pmgenmap(1), pmstat(1), PMAPI(3), pcp.conf(5) and pcp.env(5). DIAGNOSTICS
All are generated on standard error, and are intended to be self-explanatory. Performance Co-Pilot PCP PMCLIENT(1)