PCP.ENV(5)                   File Formats Manual                  PCP.ENV(5)

NAME         top

       pcp.env  -  script  to  set Performance Co-Pilot run-time environment

SYNOPSIS         top


DESCRIPTION         top

       The pcp.env script is sourced by assorted Performance Co-Pilot (PCP)
       scripts and utilities to define the PCP operating environment
       variables.  The conjugate for executable programs using the PCP
       libraries is the __pmGetConfig(3) function.

       Typical usage of pcp.env in a script is as follows :

                #! /bin/sh

                # source the PCP environment variables
                . /etc/pcp.env
                rest of script ...

       The full syntax and semantics of the pcp.conf file and the
       __pmGetConfig function are described in their respective reference

       If the file $HOME/.pcp/pcp.conf exists then this will be processed
       after the system-wide pcp.conf file.  This provides a mechanism to
       selectively modify or augment the environment settings for PCP
       scripts, which maybe useful if the scripts are run with sudo(1) which
       cleans the environment of important settings that are required to
       ensure the correct execution of the PCP scripts, e.g.  $PATH or

ENVIRONMENT         top

       The PCP_CONF environment variable specifies an alternative path to
       the pcp.conf file.

SEE ALSO         top

       PCPIntro(1), sudo(1), PCPIntro(3), PMAPI(3), __pmGetConfig(3) and

COLOPHON         top

       This page is part of the PCP (Performance Co-Pilot) project.
       Information about the project can be found at ⟨⟩.
       If you have a bug report for this manual page, send it to  This page was obtained from the project's upstream
       Git repository ⟨⟩ on
       2019-05-09.  (At that time, the date of the most recent commit that
       was found in the repository was 2019-05-08.)  If you discover any
       rendering problems in this HTML version of the page, or you believe
       there is a better or more up-to-date source for the page, or you have
       corrections or improvements to the information in this COLOPHON
       (which is not part of the original manual page), send a mail to

Performance Co-Pilot                 PCP                          PCP.ENV(5)

Pages that refer to this page: chkhelp(1)collectl2pcp(1)dbpmda(1)genpmda(1)mkaf(1)newhelp(1)pcp(1)pcpintro(1)pcp-iostat(1)pcp-kube-pods(1)pcp-tapestat(1)pmafm(1)pmcd(1)pmcd_wait(1)pmchart(1)pmclient(1)pmconfig(1)pmcpp(1)pmdaapache(1)pmdacisco(1)pmdadocker(1)pmdajbd2(1)pmdakernel(1)pmdalmsensors(1)pmdalogger(1)pmdalustrecomm(1)pmdamailq(1)pmdammv(1)pmdamounts(1)pmdanvidia(1)pmdaperfevent(1)pmdapipe(1)pmdapodman(1)pmdaproc(1)pmdaroomtemp(1)pmdarpm(1)pmdasample(1)pmdasimple(1)pmdasystemd(1)pmdate(1)pmdaxfs(1)pmdbg(1)pmdiff(1)pmdumplog(1)pmerr(1)pmfind(1)pmgenmap(1)pmgetopt(1)pmhostname(1)pmie(1)pmiestatus(1)pminfo(1)pmjson(1)pmlc(1)pmlogcheck(1)pmlogconf(1)pmlogextract(1)pmlogger(1)pmloglabel(1)pmlogreduce(1)pmlogrewrite(1)pmmgr(1)pmnewlog(1)pmnsadd(1)pmnscomp(1)pmnsdel(1)pmnsmerge(1)pmpost(1)pmprobe(1)pmproxy(1)pmsignal(1)pmstat(1)pmval(1)pmwebd(1)pcpintro(3)pmapi(3)pmdiscoverservices(3)pmgetarchiveend(3)pmgetarchivelabel(3)pmgetchildren(3)pmgetchildrenstatus(3)pmgetconfig(3)pmgetcontexthostname(3)pmgetindom(3)pmgetindomarchive(3)pmgetpmnslocation(3)pmidstr(3)pmindomstr(3)pmloadasciinamespace(3)pmloadnamespace(3)pmlocaltime(3)pmlookupdesc(3)pmlookupindom(3)pmlookupindomarchive(3)pmlookupindomtext(3)pmlookupname(3)pmlookuptext(3)pmnameall(3)pmnameid(3)pmnameindom(3)pmnameindomarchive(3)pmnewcontext(3)pmnewcontextzone(3)pmnewzone(3)LOGARCHIVE(5)mmv(5)pcp.conf(5)pmns(5)