* instance executes.  Only settings of the
                form "PMLOGGER_VARIABLE=value" will be honoured.
    
           **./pmlogger.log**
                (or **$PCP_ARCHIVE_DIR/**_< hostname>_**/pmlogger.log** when started
                automatically by either **$PCP_RC_DIR/pmlogger** or one of the
                [pmlogger(1)](../man1/pmlogger.1.html) monitoring scripts such as [pmlogger_check(1)](../man1/pmlogger_check.1.html))
                all messages and diagnostics are directed here
    

##  ENVIRONMENT  top

    
    
           Normally **pmlogger** creates a socket to receive control messages
           from [pmlc(1)](../man1/pmlc.1.html) on the first available TCP/IP port numbered 4330 or
           higher.  The environment variable **PMLOGGER_PORT** may be used to
           specify an alternative starting port number.
    
           If set to the value 1, the **PMLOGGER_LOCAL** environment variable
           will cause **pmlogger** to run in a localhost-only mode of operation,
           where it binds only to the loopback interface.
    
           The **PMLOGGER_REQUEST_TIMEOUT** variable may be set by applications
           such as [pmlc(1)](../man1/pmlc.1.html) to specify a timeout in seconds for connection
           requests to the **pmlogger** control port.  If not set, connections
           may block indefinitely.  This variable would not normally be set
           by **pmlogger** itself.
    
           The **PMLOGGER_MAXPENDING** variable can be set to indicate the
           maximum length to which the queue of pending **pmlc** connections may
           grow.
    
           The default sampling interval used by **pmlogger** can be set using
           the **PMLOGGER_INTERVAL** variable (if not set, 60 seconds will be
           used).  Both the command line and directives in the configuration
           file will override this value.  It is an integer in units of
           seconds.
    
           On platforms using [systemd(1)](../man1/systemd.1.html), and when the **-N** option is given,
           the **NOTIFY_SOCKET** environment variable would normally be set by
           the service manager prior to launching **pmlogger**.
    

##  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

    
    
           [PCPIntro(1)](../man1/PCPIntro.1.html), [pmcd(1)](../man1/pmcd.1.html), [pmdumplog(1)](../man1/pmdumplog.1.html), [pmlc(1)](../man1/pmlc.1.html), [pmlogger_check(1)](../man1/pmlogger_check.1.html),
           [pmlogger_daily(1)](../man1/pmlogger_daily.1.html), [systemctl(1)](../man1/systemctl.1.html), [systemd(1)](../man1/systemd.1.html), [execvp(3)](../man3/execvp.3.html), [PMAPI(3)](../man3/PMAPI.3.html),
           [__pmServerNotifyServiceManagerReady(3)](../man3/__pmServerNotifyServiceManagerReady.3.html), [pmSpecLocalPMDA(3)](../man3/pmSpecLocalPMDA.3.html),
           [strftime(3)](../man3/strftime.3.html), [pcp.conf(5)](../man5/pcp.conf.5.html), [pcp.env(5)](../man5/pcp.env.5.html), **pmlogger**(5), [PMNS(5)](../man5/PMNS.5.html),
           **chkconfig**(8) and [cron(8)](../man8/cron.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 pcp@groups.io.  This page was obtained from the
           project's upstream Git repository
           â¨<https://github.com/performancecopilot/pcp.git>â© on 2023-12-22.
           (At that time,