pmlogger_rewrite(1) — Linux manual page


PMLOGGER_REWRITE(1)        General Commands Manual       PMLOGGER_REWRITE(1)

NAME         top

       pmlogger_rewrite  - helper script to rewrite Performance Co-Pilot ar‐

SYNOPSIS         top

       $PCP_BINADM_DIR/pmlogger_rewrite [-dNsVvw?]  [-c config] archive ...

DESCRIPTION         top

       pmlogger_rewrite is a helper script that is used by pmlogger_daily(1)
       when rewriting Performance Co-Pilot (PCP) archives.  Rewriting is
       usually required to accommodate evolutionary changes in metadata so
       old archives can be updated and then merged with current archives.

       pmlogger_rewrite is a wrapper script for pmlogrewrite(1) that will
       potentially rewrite all of the archive logs matching the archive
       arguments.  Each archive argument may be a PCP archive file name, the
       basename for the files in a PCP archive, or a directory (in which
       case all subordinate PCP archives are found by recursive descent).

       pmlogrewrite is run with the -i option so rewriting is done ``in
       place''.  The -q option is also used, so if no rewriting is required
       then no changes are made to the archive files.

OPTIONS         top

       The following options are passed through to pmlogrewrite: -c, -d, -s,
       -v and -w.  Refer to pmlogrewrite(1) for the meaning of these

       The remaining options are:

       -N, --showme
            Runs pmlogger_rewrite in a ``show me'' or ``dry run'' mode where
            the tasks that would be performed are reported, but no changes
            are made.  This is typically used for debugging in combination
            with one (verbose) or two (very verbose) -V options.

       -V, --verbose
            Increase script output verbosity.

       -?, --help
            Display usage message and exit.


       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).

SEE ALSO         top

       PCPIntro(1), pmlogger(1), pmlogger_daily(1) and pmlogrewrite(1).

COLOPHON         top

       This page is part of the PCP (Performance Co-Pilot) project.
       Information about the project can be found at ⟨⟩.
       If you have a bug report for this manual page, send it to  This page was obtained from the project's upstream
       Git repository ⟨⟩ on
       2020-08-13.  (At that time, the date of the most recent commit that
       was found in the repository was 2020-08-11.)  If you discover any
       rendering problems in this HTML version of the page, or you believe
       there is a better or more up-to-date source for the page, or you have
       corrections or improvements to the information in this COLOPHON
       (which is not part of the original manual page), send a mail to

Performance Co-Pilot                 PCP                 PMLOGGER_REWRITE(1)