pmbrand(1)

pmbrand - brand Performance Co-Pilot licenses

As shipped in IRIX 6.5.30. Last changed in IRIX 6.5.30.

This page could not be fully tidied (pagination-warning, no-header); it is shown as printed.

NAME
     pmbrand - brand Performance Co-Pilot licenses

SYNOPSIS
     $PCP_BINADM_DIR/pmbrand [-lqv]

DESCRIPTION
     pmbrand manages the ``branded'' file of valid Performance Co-Pilot (PCP)
     licenses.

     By default, pmbrand silently updates the branded file to reflect the
     local system identification and those PCP licenses that are currently
     valid.  The -l option causes some verbose output describing the
     information that will be branded.

     The -q option reports the current state of the valid PCP licenses on the
     local system, without accessing or modifying the branded file.

     Alternatively, the -v option does not modify the branded file, but
     verifies the state of the file, and exits with a status of zero if it is
     valid and up to date, else the exit status is greater than zero.

     No special privileges are required with the -q or -v options, but for
     other uses pmbrand must be run by root so the ``branded'' file can be
     updated.

     The branded file is used to select appropriate default behavior when
     loading a Performance Metrics Name Space (PMNS) using pmLoadNameSpace(3).

FILES
     $PCP_VAR_DIR/pmns/Brand
               the ``branded'' file of valid PCP licenses

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
     PCPIntro(1), PMAPI(3), pmLoadNameSpace(3), pcp.conf(4) and pcp.env(4).

DIAGNOSTICS
     Various messages indicate non-recoverable failures.  In all cases, the
     branded file will be created or modified.  This may necessitate
     correcting the problem and re-running pmbrand before PCP applications,
     and in particular calls to pmLoadNameSpace(3), will work correctly.

                                                                             1