1PMLOGMV(1) General Commands Manual PMLOGMV(1)
2
6 pmlogmv - move (rename) Performance Co-Pilot archive files
7
9 pmlogmv [-cfNV?] oldname newname
10
12 A Performance Co-Pilot (PCP) archive consists of multiple files as cre‐
13 ated by pmlogger(1). pmlogmv allows all the files of a single PCP ar‐
14 chive to be moved or renamed as a group in a single operation.
15 The oldname argument identifies the target archive, and may be either
17 the basename that is common to all files in that archive or one of the
18 archive's files. The new archive's basename is newname.
19 Because PCP archives are important records of system activity, special
21 care is taken to ensure the integrity of an archive's files. For re‐
22 coverable problems encountered during the execution of pmlogmv, all the
23 files associated with oldname will be preserved, and no new files with
24 the newname prefix will be created. ``Recoverable problems'' include
25 signals that can be caught (such as SIGHUP, SIGINT, SIGQUIT and
26 SIGTERM), permissions issues, new files already existing, file system
27 full events, etc.
28 The implementation of pmlogmv tries to use hard links in the file sys‐
30 tem and so follows the semantic restrictions of ln(2) which for most
31 systems means the directories containing both the oldname and the new‐
32 name PCP archive files need to be within the same file system. When
33 this is not possible, pmlogmv falls back to using cp(1) to copy oldname
34 to newname.
35
37 The available command line options are:
38 -c, --checksum
40 Paranoid checking mode when cp(1) is needed and each file's check‐
41 sum is computed for the original file and the copied file, and the
42 checksums must match before the copy is considered acceptable.
43 The checksum command is chosen by trying the following in turn un‐
44 til one is found to be executable: md5sum(1), sha256sum(1),
45 sha1sum(1) and sum(1). If no executable checksum command is
46 found, a warning is issued and the checksum check is skipped.
47 -f, --force
49 Normally pmlogmv takes a conservative view in respect of newname
50 and will not proceed if newname contains any characters that are
51 likely to cause a problem for sh(1). This includes ``glob'' char‐
52 acters like ``?'', ``*'' and ``['', shell syntax meta characters
53 like ``('', ``|'', ``;'' and ``&'', shell I/O redirection charac‐
54 ters like ``<'' and ``>'', the dollar sign, a space, etc.
55 The -f flag forces pmlogmv to proceed, even if newname contains
57 any of these ``unsafe'' characters.
58 -N, --showme
60 Perform a dry-run, checking and reporting what changes would be
61 made without making any changes.
62 -V, --verbose
64 Enable verbose mode.
65 -?, --help
67 Display usage message and exit.
68
70 All error and warning messages are intended to be easily understood and
71 errors produce a non-zero exit status.
72
74 cp(1), ln(1), md5sum(1), PCPIntro(1), pmlogger(1), sha1sum(1),
75 sha256sum(1) and LOGARCHIVE(5).
76Performance Co-Pilot PCP PMLOGMV(1)