1PMNSADD(1) General Commands Manual PMNSADD(1)
2
6 pmnsadd - add new names to the Performance Co-Pilot PMNS
7
9 $PCP_BINADM_DIR/pmnsadd [-d] [-n namespace] file
10
12 pmnsmerge(1) performs the same function as pmnsadd and is faster, more
13 robust and more flexible. It is therefore recommended that pmnsmerge(1)
14 be used instead.
15 pmnsadd adds subtree(s) of new names into a Performance Metrics Name
17 Space (PMNS), as used by the components of the Performance Co-Pilot
18 (PCP).
19 Normally pmnsadd operates on the default Performance Metrics Namespace
21 (PMNS), however if the -n option is specified an alternative namespace
22 is used from the file namespace.
23 The default PMNS is found in the file $PCP_VAR_DIR/pmns/root unless the
25 environment variable PMNS_DEFAULT is set, in which case the value is
26 assumed to be the pathname to the file containing the default PMNS.
27 The new names are specified in the file, arguments and conform to the
29 syntax for PMNS specifications, see pmns(4). There is one PMNS subtree
30 in each file, and the base PMNS pathname to the inserted subtree is
31 identified by the first group named in each file, e.g. if the specifi‐
32 cations begin
33 myagent.foo.stuff {
35 mumble 123:45:1
36 fumble 123:45:2
37 }
38 then the new names will be added into the PMNS at the non-leaf position
40 identified by myagent.foo.stuff, and following all other names with the
41 prefix myagent.foo.
42 The new names must be contained within a single subtree of the names‐
44 pace. If disjoint subtrees need to be added, these must be packaged
45 into separate files and pmnsadd used on each, one at a time.
46 All of the files defining the PMNS must be located within the directory
48 that contains the root of the PMNS, this would typically be
49 $PCP_VAR_DIR/pmns for the default PMNS, and this would typically imply
50 running pmnsadd as root.
51 As a special case, if file contains a line that begins root { then it
53 is assumed to be a complete PMNS that needs to be merged, so none of
54 the subtree extraction and rewriting is performed and file is handed
55 directly to pmnsmerge(1).
56 Provided some initial integrity checks are satisfied, pmnsadd will
58 update the PMNS using pmnsmerge(1) - if this fails for any reason, the
59 original namespace remains unchanged.
60 The -d option allows the resultant PMNS to optionally contain duplicate
62 PMIDs with different names in the PMNS. By default this condition is
63 considered an error.
64
66 Once the writing of the new namespace file has begun, the signals SIG‐
67 INT, SIGHUP and SIGTERM will be ignored to protect the integrity of the
68 new files.
69
71 $PCP_VAR_DIR/pmns/root the default PMNS, when then environment vari‐
72 able PMNS_DEFAULT is unset
73
75 Environment variables with the prefix PCP_ are used to parameterize the
76 file and directory names used by PCP. On each installation, the file
77 /etc/pcp.conf contains the local values for these variables. The
78 $PCP_CONF variable may be used to specify an alternative configuration
79 file, as described in pcp.conf(4).
80
82 pmnscomp(1), pmnsdel(1), pmnsmerge(1), pcp.conf(4), pcp.env(4) and
83 pmns(4).
84Performance Co-Pilot SGI PMNSADD(1)