NAME
pmnsadd - add new names to the Performance Co-Pilot PMNS
SYNOPSIS
$PCP_BINADM_DIR/pmnsadd [-d] [-n namespace] file
DESCRIPTION
pmnsmerge(1) performs the same function as pmnsadd and is
faster, more robust and more flexible. It is therefore
recommended that pmnsmerge(1) be used instead.
pmnsadd adds subtree(s) of new names into a Performance
Metrics Name Space (PMNS), as used by the components of
the Performance Co-Pilot (PCP).
Normally pmnsadd operates on the default Performance Met
rics Namespace (PMNS), however if the -n option is speci
fied an alternative namespace is used from the file names
pace.
The default PMNS is found in the file
$PCP_VAR_DIR/pmns/root unless the environment variable
PMNS_DEFAULT is set, in which case the value is assumed to
be the pathname to the file containing the default PMNS.
The new names are specified in the file, arguments and
conform to the syntax for PMNS specifications, see
pmns(4). There is one PMNS subtree in each file, and the
base PMNS pathname to the inserted subtree is identified
by the first group named in each file, e.g. if the speci
fications begin
myagent.foo.stuff {
mumble 123:45:1
fumble 123:45:2
}
then the new names will be added into the PMNS at the non-
leaf position identified by myagent.foo.stuff, and follow
ing all other names with the prefix myagent.foo.
The new names must be contained within a single subtree of
the namespace. If disjoint subtrees need to be added,
these must be packaged into separate files and pmnsadd
used on each, one at a time.
All of the files defining the PMNS must be located within
the directory that contains the root of the PMNS, this
would typically be $PCP_VAR_DIR/pmns for the default PMNS,
and this would typically imply running pmnsadd as root.
Provided some initial integrity checks are satisfied,
fails for any reason, the original namespace remains
unchanged.
The -d option allows the resultant PMNS to optionally con
tain duplicate PMIDs with different names in the PMNS. By
default this condition is considered an error.
CAVEAT
Once the writing of the new namespace file has begun, the
signals SIGINT, SIGHUP and SIGTERM will be ignored to pro
tect the integrity of the new files.
FILES
$PCP_VAR_DIR/pmns/root the default PMNS, when then envi
ronment variable PMNS_DEFAULT is
unset
PCP ENVIRONMENT
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(4).
SEE ALSO
pmnscomp(1), pmnsdel(1), pmnsmerge(1), pcp.conf(4),
pcp.env(4) and pmns(4).
Man(1) output converted with
man2html