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

NAME

6       pmlogger_merge - helper script to merge Performance Co-Pilot archives
7

SYNOPSIS

9       $PCP_BINADM_DIR/pmlogger_merge  [-fNVE?]   [input-basename  ... output-
10       name]
11

DESCRIPTION

13       pmlogger_merge is a helper script that  is  used  by  pmlogger_daily(1)
14       when  merging all of the Performance Co-Pilot (PCP) archives for a sin‐
15       gle host on a single day into a combined PCP archive.
16
17       pmlogger_merge is a wrapper script for pmlogextract(1) that merges  all
18       of  the archive logs matching the input-basename arguments, and creates
19       a new archive using output-name as the base name for the physical files
20       that  constitute an archive log.  The input-basename arguments may con‐
21       tain meta characters in the style of sh(1).
22

OPTIONS

24       The available command line options are:
25
26       -f, --force
27            This option causes all of the input files to be removed  once  the
28            output archive has been created.
29
30       -N, --showme
31            Runs pmlogger_merge in a ``show me'' or ``dry run'' mode where the
32            tasks that would be performed are reported,  but  no  changes  are
33            made.   This  is  typically used for debugging in combination with
34            one (verbose) or two (very verbose) -V options.
35
36       -V, --verbose
37            Increase verbosity in the output progress report.
38
39       -E, --expunge
40            When metric metadata differences are encountered between  archives
41            to  be merged, the default behaviour is for pmlogger_merge to fail
42            with a fatal error and the output-name  archive  is  not  created.
43            The  -E  flag  instead  issues a warning and excludes the affected
44            metrics from the merged output  archive.   This  is  intended  for
45            automated  daily  log  rotation  where  it is highly desirable for
46            unattended daily archive merging,  rewriting  and  compression  to
47            succeed.   See  also pmlogger_daily(1) and the -x flag to pmlogex‐
48            tract(1).
49
50       -?, --help
51            Display usage message and exit.
52

PCP ENVIRONMENT

54       Environment variables with the prefix PCP_ are used to parameterize the
55       file  and  directory names used by PCP.  On each installation, the file
56       /etc/pcp.conf contains the  local  values  for  these  variables.   The
57       $PCP_CONF  variable may be used to specify an alternative configuration
58       file, as described in pcp.conf(5).
59

SEE ALSO

61       PCPIntro(1), pmlogextract(1), pmlogger(1) and pmlogger_daily(1).
62
63
64
65Performance Co-Pilot                  PCP                    PMLOGGER_MERGE(1)
Impressum