[pcp] [Bug 1130] New: pmsnap / pmlc flush / pmcd.pmlogger.* auto-logging

bugzilla-daemon at oss.sgi.com bugzilla-daemon at oss.sgi.com
Mon Dec 7 12:00:12 CST 2015


http://oss.sgi.com/bugzilla/show_bug.cgi?id=1130

            Bug ID: 1130
           Summary: pmsnap / pmlc flush / pmcd.pmlogger.* auto-logging
           Product: pcp
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: pcp
          Assignee: pcp at kenj.com.au
          Reporter: fche at redhat.com
                CC: pcp at oss.sgi.com
    Classification: Unclassified

pmlogger automagically adds pmcd.pmlogger.{host,port,archive} self-descriptions
to its output archives, though this is not documented in the pmlogger man page
and represents potentially undesirable information leakage.  (They are briefly
mentioned in pmlogextract.1.)  The only use of these metrics that a quick
git-grep identifies is in the pmsnap program, which uses the
pmcd.pmlogger.{host,port} fields to issue a 'pmlc flush'.

However, pmlc flushing has become a no-op since pmlogger started issuing
semantic writes (pcp 3.9.3ish in 2014).  Moreover, the pmcd.pmlogger.host name
has the usual FQDN risks (may have some sort host name in it, but there's no
guarantee that it is a remotely- (or even locally-) tcp/ip resolvable one).

If all this obsoleteish functionality is to be retained, please consider
documenting it in pmlogger.1.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://oss.sgi.com/pipermail/pcp/attachments/20151207/2015d219/attachment.html>


More information about the pcp mailing list