.1.html)
    
           **-p** communicate with [pmcd(1)](../man1/pmcd.1.html) via stdin/stdout
    
           **-u** expect [pmcd(1)](../man1/pmcd.1.html) to connect on given unix domain socket
    
           **-6** expect [pmcd(1)](../man1/pmcd.1.html) to connect on given ipv6 port (number or
                name)
    

##  INSTALLATION  top

    
    
           The **perfevent** PMDA is not activated by default To install the
           PMDA, do the following as root:
    
                # cd $PCP_PMDAS_DIR/perfevent
                # ./Install
    
           If you want to undo the installation, do the following as root:
    
                # cd $PCP_PMDAS_DIR/perfevent
                # ./Remove
    
           **pmdaperfevent** is launched by [pmcd(1)](../man1/pmcd.1.html) and should never be executed
           directly.  The Install and Remove scripts notify [pmcd(1)](../man1/pmcd.1.html) when the
           agent is installed or removed.
    

##  FILES  top

    
    
           **$PCP_PMCDCONF_PATH**
                  command line options used to launch **pmdaperfevent**
           **$PCP_PMDAS_DIR/perfevent/perfevent.conf**
                  default configuration file for the PMDA.  See
                  [perfevent.conf(5)](../man5/perfevent.conf.5.html) for detailed information.
           **$PCP_PMDAS_DIR/perfevent/help**
                  default help text file for the perfevent metrics
           **$PCP_PMDAS_DIR/perfevent/Install**
                  installation script for the **pmdaperfevent** agent
           **$PCP_PMDAS_DIR/perfevent/Remove**
                  undo installation script for the **pmdaperfevent** agent
           **$PCP_LOG_DIR/pmcd/perfevent.log**
                  default log file for error messages and other information
                  from **pmdaperfevent**
    

##  UPGRADING  top

    
    
           Some metric names have changed starting in version 3.10.8 to
           better conform to PMNS conventions.  [pmlogrewrite(1)](../man1/pmlogrewrite.1.html) can be used
           to update old archives.  A helper utility,
           **$PCP_PMDAS_DIR/perfevent/perfevent-makerewrite.pl** will generate a
           config file that is suitable for use with [pmlogrewrite(1)](../man1/pmlogrewrite.1.html) to
           update the metric names in existing archives.
    

##  BUGS  top

    
    
           Each event is placed in its own group and there is no way to
           group related events together so they are guaranteed to be
           simultaneously active.  A workaround for this is to ensure that
           the number of configured events is less than or equal to the
           number of available hardware counters.  This means that the
           events will not be time-multiplexed by the kernel and will be
           simultaneously active.
    

##  PCP ENVIRONMENT  top

    
    
           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(5)](../man5/pcp.conf.5.html).
    

##  SEE ALSO  top

    
    
           [perfalloc(1)](../man1/perfalloc.1.html), [perfevent.conf(5)](../man5/perfevent.conf.5.html), [PCPIntro(1)](../man1/PCPIntro.1.html), [pmcd(1)](../man1/pmcd.1.html),
           [pmlogrewrite(1)](../man1/pmlogrewrite.1.html), [PMAPI(3)](../man3/PMAPI.3.html), [pcp.conf(5)](../man5/pcp.conf.5.html), [pcp.env(5)](../man5/pcp.env.5.html) and [sysctl(8)](../man8/sysctl.8.html).
    

##  COLOPHON  top

    
    
           This page is part of the _PCP_ (Performance Co-Pilot) project.
           Information about the project can be found at 
           â¨<http://www.pcp.io/>â©.  If you have a bug report for this manual
           page, send it to