pmnsdel(1) [centos man page]

PMNSDEL(1)						      General Commands Manual							PMNSDEL(1)

NAME

       pmnsdel - delete a subtree of names from the Performance Co-Pilot PMNS

SYNOPSIS

       $PCP_BINADM_DIR/pmnsdel [-d] [-n namespace] metricpath [ ... ]

DESCRIPTION

       pmnsdel	removes  subtrees  of  names  from  a Performance Metrics Name Space (PMNS), as used by the components of the Performance Co-Pilot
       (PCP).

       Normally pmnsdel operates on the default Performance Metrics Namespace (PMNS), however if the -n option is specified an alternative  names-
       pace is used from the file namespace.

       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 metric names to be deleted are all those for which one of the metricpath arguments is a prefix in the PMNS, see pmns(5).

       All of the files defining the PMNS must be located within the directory that contains the root of the PMNS, and	this  would  typically	be
       $PCP_VAR_DIR/pmns for the default PMNS, and this would typically imply running pmnsdel as root.

       Provided  some  initial	integrity  checks are satisfied, pmnsdel will update the necessary PMNS files.	Should an error be encountered the
       original namespace is restored.	Note that any PMNS files that are no longer referenced by the modified namespace will not be removed, even
       though their contents are not part of the new namespace.

       The  -d option allows the resultant PMNS to optionally contain 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 protect	the  integrity	of
       the new files.

FILES

       $PCP_VAR_DIR/pmns/root	the default PMNS, when then environment 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	configura-
       tion file, as described in pcp.conf(5).

SEE ALSO

       pmnsadd(1), pmnsmerge(1), pcp.conf(5), pcp.env(5) and pmns(5).

Performance Co-Pilot							PCP								PMNSDEL(1)

PMNSMERGE(1)						      General Commands Manual						      PMNSMERGE(1)

NAME

       pmnsmerge - merge multiple versions of a Performance Co-Pilot PMNS

SYNOPSIS

       $PCP_BINADM_DIR/pmnsmerge [-adfv] infile [...]  outfile

DESCRIPTION

       pmnsmerge  merges  multiple  instances  of  a  Performance Metrics Name Space (PMNS), as used by the components of the Performance Co-Pilot
       (PCP).

       Each infile argument names a file that includes the root of a PMNS, of the form

		 root {
		     /* arbitrary stuff */
		 }

       The order in which the infile files are processed is determined by the presence or absence of embedded control lines of	the  form  #define
       _DATESTAMP YYYYMMDD

       Files  without  a control line are processed first and in the order they appear on the command line.  The other files are then processed in
       order of ascending _DATESTAMP.

       The -a option suppresses the argument re-ordering and processes all files in the order they appear on the command line.

       The merging proceeds by matching names in PMNS, only those new names in each PMNS are considered, and these are added  after  any  existing
       metrics with the longest possible matching prefix in their names.  For example, merging these two input PMNS

		 root { 		   root {
					       surprise  1:1:3
		     mine	1:1:1	       mine	 1:1:1
		     foo		       foo
					       yawn
		     yours	1:1:2
		 }			   }
		 foo {			   foo {
		     fumble	1:2:1
					       mumble	 1:2:3
		     stumble	1:2:2	       stumble	 1:2:2
		 }			   }
					   yawn {
					       sleepy	 1:3:1
					   }

       Produces the resulting PMNS in out.

		 root {
		     mine      1:1:1
		     foo
		     yours     1:1:2
		     surprise  1:1:3
		     yawn
		 }
		 foo {
		     fumble    1:2:1
		     stumble   1:2:2
		     mumble    1:2:3
		 }
		 yawn {
		     sleepy    1:3:1
		 }

       To  avoid  accidental over-writing of PMNS files, outfile is expected to not exist when pmnsmerge starts.  The -f option forces the removal
       of outfile (if it exists), before the check is made.

       The -d option allows the resultant PMNS to optionally contain duplicate PMIDs with different names in the PMNS.	By default this  condition
       is considered an error.

       The -v option produces one line of diagnostic output as each infile is processed.

       Once  all of the merging has been completed, pmnsmerge will attempt to load the resultant namespace using pmLoadASCIINameSpace(3) - if this
       fails for any reason, outfile will still be created, but pmnsmerge will report the problem and exit with non-zero status.

CAVEAT

       Once the writing of the new outfile file has begun, the signals SIGINT, SIGHUP and SIGTERM will be ignored to protect the integrity of  the
       new file.

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	configura-
       tion file, as described in pcp.conf(5).

SEE ALSO

       pmnsadd(1), pmnsdel(1), pmLoadASCIINameSpace(3), pcp.conf(5), pcp.env(5) and pmns(5).

Performance Co-Pilot							PCP							      PMNSMERGE(1)