MKAF(1)

๐Ÿ“ฆ
version 7.2.2 ยท 3 versions
, in arch rolling, centos-stream 10, centos-stream 9, debian trixie, fedora 43, fedora 44, ubuntu questing, ubuntu resolute, ubuntu stonking

๐Ÿ’– MKAF(1) โ€” like, the manual page for mkaf, bestie ๐Ÿ’–

General Commands Manual โœจ PCP vibes only


๐ŸŒธ NAME ๐ŸŒธ

mkaf โ€” create a Performance Co-Pilot archive folio ๐Ÿซถ


โœจ SYNOPSIS โœจ

$PCP_BINADM_DIR/mkaf [-?] [findopts] filename ...

๐Ÿฆ‹ DESCRIPTION ๐Ÿฆ‹

okay so picture this: you've got a whole collection of one or more Performance Co-Pilot archives (peep PCPIntro(1) for the lore), and mkaf is the girl who combines them into a PCP archive folio plus the associated archive folio control file. iconic behaviour, no cap. some PCP tools literally use mkaf to make archive folios โ€” like the ``record'' facility in the pmchart(1) and pmview(1) tools โ€” all so playback with pmafm(1) is smooth. ๐Ÿ’…

mkaf goes through each filename argument one by one, and if that thing is a component file from a PCP archive, then boom ๐Ÿ’ฅ that archive gets added to the folio.

if filename is a directory, bestie, it gets searched recursively using find(1). and any filename argument that starts with a ``-'' is assumed to be a find(1) command line option (findopts) โ€” the default is -follow if you don't specify any findopts. periodt.

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. that's the main character archive, basically. ๐Ÿ‘‘

the folio control file gets written to standard output, and it has this exact 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

๐ŸŽ€ OPTIONS ๐ŸŽ€

the available command line options are, bestie:

  • -? โ€” display the usage message and exit. bye ๐Ÿ‘‹
  • -findopts โ€” options to be passed to find(1). the default is -follow.

๐Ÿ’€ DIAGNOSTICS ๐Ÿ’€

some informational messages, warnings and pathological conditions get reported on standard error. not everything can be cute, unfortunately. ๐Ÿ™ˆ


๐ŸŒˆ 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 configuration file, as described in pcp.conf(5). iykyk ๐Ÿ’œ


๐ŸŒŸ SEE ALSO ๐ŸŒŸ

find(1), PCPIntro(1), pmafm(1), pmchart(1), pmview(1), pcp.conf(5) and pcp.env(5). go read them, they're giving knowledge. ๐Ÿ“šโœจ


Performance Co-Pilot ๐Ÿฆ‹ PCP ๐Ÿฆ‹ MKAF(1)

and that's the whole page, bestie โ€” mwah, slay, go make some archive folios ๐Ÿ’–โœจ๐ŸŽ€๐Ÿซถ

๐Ÿ“ฆ where this page comes from