_$PCP_LOG_DIR/pmlogger/pmlogger_daily.log_
                if the previous execution of **pmlogger_daily** produced any
                output it is saved here.  The normal case is no output in
                which case the file does not exist.
    
           _$PCP_ARCHIVE_DIR/ <hostname>/SaveLogs_
                if this directory exists, then the log file from the **-l**
                argument of a newly launched [pmlogger(1)](../man1/pmlogger.1.html) for _hostname_ will
                be linked into this directory with the name _archive_**.log**
                where _archive_ is the basename of the associated [pmlogger(1)](../man1/pmlogger.1.html)
                PCP archive files.  This allows the log file to be inspected
                at a later time, even if several [pmlogger(1)](../man1/pmlogger.1.html) instances for
                _hostname_ have been launched in the interim.  Because the PCP
                archive management tools run under the uid of the user
                ``pcp'', _$PCP_ARCHIVE_DIR/ <hostname>/SaveLogs_ typically
                needs to be owned by the user ``pcp''.
    
           _$PCP_LOG_DIR/pmlogger/.NeedRewrite_
                if this file exists, then this is treated as equivalent to
                using **-R** on the command line and the file will be removed
                once all rewriting has been done.
    

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

##  COMPATIBILITY ISSUES  top

    
    
           Earlier versions of **pmlogger_daily** used [find(1)](../man1/find.1.html) to locate files
           for compressing or culling and the **-k** and **-x** options took only
           integer values to mean ``days''.  The semantics of this was quite
           loose given that [find(1)](../man1/find.1.html) offers different precision and semantics
           across platforms.
    
           The current implementation of **pmlogger_daily** uses [find-filter(1)](../man1/find-filter.1.html)
           which provides high precision intervals and semantics that are
           relative to the time of execution and are consistent across
           platforms.
    

##  SEE ALSO  top

    
    
           **egrep**(1), [find-filter(1)](../man1/find-filter.1.html), [PCPIntro(1)](../man1/PCPIntro.1.html), [pmconfig(1)](../man1/pmconfig.1.html), [pmlc(1)](../man1/pmlc.1.html),
           [pmlogconf(1)](../man1/pmlogconf.1.html), [pmlogctl(1)](../man1/pmlogctl.1.html), [pmlogextract(1)](../man1/pmlogextract.1.html), [pmlogger(1)](../man1/pmlogger.1.html),
           [pmlogger_check(1)](../man1/pmlogger_check.1.html), [pmlogger_daily_report(1)](../man1/pmlogger_daily_report.1.html), [pmlogger_merge(1)](../man1/pmlogger_merge.1.html),
           [pmlogmv(1)](../man1/pmlogmv.1.html), [pmlogrewrite(1)](../man1/pmlogrewrite.1.html), [systemd(1)](../man1/systemd.1.html), **xz**(1) 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, the date of the most recent commit that was found
           in the repository was 2023-12-16.)  If you discover any rendering
           problems in this HTML version of the page, or you be