pmtraversepmns(3) [centos man page]

PMTRAVERSEPMNS(3)					     Library Functions Manual						 PMTRAVERSEPMNS(3)

NAME

       pmTraversePMNS, pmTraversePMNS_r - traverse the performance metrics name space

C SYNOPSIS

       #include <pcp/pmapi.h>

       int pmTraversePMNS(const char *name, void (*dometric)(const char *));
       int pmTraversePMNS_r(const char *name, void (*dometric_r)(const char *, void *), void *closure);

       cc ... -lpcp

DESCRIPTION

       The routine pmTraversePMNS may be used to perform a depth-first traversal of the Performance Metrics Name Space (PMNS).

       The  traversal  starts at the node identified by name - if name is an empty string (i.e. ""), the traversal starts at the root of the PMNS.
       Usually name would be the pathname of a non-leaf node in the PMNS.

       For each leaf node (i.e. performance metric) found in the traversal, the user-supplied routine dometric is called with the full pathname of
       that  metric  in  the PMNS as the single argument.  This argument is null-byte terminated, and is constructed from a buffer that is managed
       internally to pmTraversePMNS.  Consequently the value is only valid during the call to dometric - if the pathname needs to be retained,	it
       should be copied using strdup(3C) before returning from dometric.

       The pmTraversePMNS_r routine performs the same function, except the callback method func_r has an additional parameter that will be closure
       from the initial call to pmTraversePMNS_r.  The additional parameter to pmTraversePMNS_r and the callback method allows the caller to  pass
       context	through pmTraversePMNS_r and into the callback method func_r, making the service more useful for multi-threaded applications where
       thread-private data can be accessed in the callback method via the closure argument.

       On success pmTraversePMNS returns the number of children of name, which may be zero.

SEE ALSO

       PMAPI(3) and pmGetChildren(3).

DIAGNOSTICS

       PM_ERR_NOPMNS
	      Failed to access a PMNS for operation.  Note that if the application hasn't a priori called pmLoadNameSpace(3) and wants to use  the
	      distributed PMNS, then a call to pmTraversePMNS must be made inside a current context.

       PM_ERR_NAME
	      The initial pathname name is not valid in the current PMNS.

       PM_ERR_*
	      Other diagnostics are for protocol failures when accessing the distributed PMNS.

Performance Co-Pilot							PCP							 PMTRAVERSEPMNS(3)

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)