Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

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

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)
Man Page