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

PMAFM(1)						      General Commands Manual							  PMAFM(1)

NAME
pmafm - Performance Co-Pilot archive folio manager SYNOPSIS
pmafm folioname [command [arg ...]] DESCRIPTION
A collection of one or more Performance Co-Pilot (PCP) archive logs may be combined with a control file to produce a PCP archive folio. Archive folios are created using either mkaf(1) or the interactive ``record mode'' services of PCP clients like pmchart(1). pmafm provides a number of services that may be used to process folios. In particular, it provides support for execution of PCP tools using one or more of the component archive logs within an archive folio. The target folio is identified by the folio control file folioname. The syntax for a folio control file is described in mkaf(1). If present, the command and arguments following folioname are interpreted and executed as a single command, otherwise commands are read from standard input. The following commands are supported. archives Subsequent commands apply to all archives in the folio. archives N[,...] Archives within a folio are numbered 1, 2, etc. Subsequent commands are restricted to apply only to the designated archives. archives name[,...] Archives within a folio have unique names. Subsequent commands are restricted to apply only to the designated archives. check Validate the presence and format of each file in the folio and the component archives. help A brief reminder of the command syntax. ? is a synonym for help. hosts Subsequent commands apply to all archives in the folio. hosts hostname[,...] Subsequent commands are restricted to apply only to those archives that match the designated hostnames. list [verbose] Display the contents of the folio. By default the control header and the ordinal number, hostname and archive base name for each archive in the folio. The verbose option causes pmafm to dump the label record from each archive using pmdumplog -l. 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. quit Exit pmafm. remove Echo on standard output the sh(1) commands required to remove all of the physical files associated with this archive folio. repeat tool [arg ...] Execute the known PCP tool once per selected archive. For example, the command repeat pmval -t60 kernel.all.load would run pmval(1) once per archive, with an appropriate -a argument. replay Some archive folios are created by tools (e.g. pmchart(1)) that provide sufficient information to allow all of the information in all of the archives of a folio to be replayed. [run] tool [arg ...] Execute the known PCP tool on the selected archives. Some PCP tools are able to process multiple concurrent archives, and in this case the tool is run once with the list of all selected archives passed via a -a argument. Otherwise, this command is synonymous with repeat. selections Display those archives that would be selected for processing with a repeat, replay or run command. The restrictions via any hosts and archives commands are conjuncted. These restrictions serve to limit the specific archives processed in the subsequent repeat, replay, run and selections commands. By default, all archives are selected. Keywords in commands may be abbreviated provided no ambiguity is introduced, e.g. help, hel and he are synonymous, but h is ambiguous. FILES
$PCP_SYSCONF_DIR/pmafm/* control files that define the behavior of each PCP tool known to pmafm. This information may be customized or extended, see $PCP_SYSCONF_DIR/pmafm/pcp for documentation of the syntax and semantics of these files. $HOME/.pcp/pmafm/* User customization of the control files. All files in this directory are treated in the same manner as control files in the $PCP_SYSCONF_DIR/pmafm directory. 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
mkaf(1), pmchart(1), pmview(1), PMAPI(3), pmRecordSetup(3), pcp.conf(5) and pcp.env(5). DIAGNOSTICS
Many, but all are intended to be easily understood. Performance Co-Pilot PCP PMAFM(1)
Man Page