1PMLOGGER_REWRITE(1) General Commands Manual PMLOGGER_REWRITE(1)
2
6 pmlogger_rewrite - helper script to rewrite Performance Co-Pilot ar‐
7 chives
8
10 $PCP_BINADM_DIR/pmlogger_rewrite [-dNsVvw] [-c config] archive ...
11
13 pmlogger_rewrite is a helper script that is used by pmlogger_daily(1)
14 when rewriting Performance Co-Pilot (PCP) archives. Rewriting is usu‐
15 ally required to accommodate evolutionary changes in metadata so old
16 archives can be updated and then merged with current archives.
17 pmlogger_rewrite is a wrapper script for pmlogrewrite(1) that will
19 potentially rewrite all of the archive logs matching the archive argu‐
20 ments. Each archive argument may be a PCP archive file name, the base‐
21 name for the files in a PCP archive, or a directory (in which case all
22 subordinate PCP archives are found by recursive descent).
23 pmlogrewrite (1) is run with the -i option so rewiting is done ``in
25 place'' and the -q option so if no rewriting is required then no
26 changes are made to the archive files.
27 Using -N option runs pmlogger_rewrite in a ``show me'' or ``dry run''
29 mode where the tasks that would be performed are reported, but no
30 changes are made. This is typically used for debugging in combination
31 with one (verbose) or two (very verbose) -V options.
32 The following options are passed through to pmlogrewrite: -c, -d, -s,
34 -v and -w. Refer to pmlogrewrite(1) for the meaning of these options.
35
38 Environment variables with the prefix PCP_ are used to parameterize the
39 file and directory names used by PCP. On each installation, the file
40 /etc/pcp.conf contains the local values for these variables. The
41 $PCP_CONF variable may be used to specify an alternative configuration
42 file, as described in pcp.conf(5).
43
45 PCPIntro(1), pmlogger(1), pmlogger_daily(1) and pmlogrewrite(1).
46Performance Co-Pilot PCP PMLOGGER_REWRITE(1)