Bug 1309190 - PCP -S can't be used in live mode
PCP -S can't be used in live mode
Product: Fedora
Classification: Fedora
Component: pcp (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Nathan Scott
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-02-17 01:52 EST by Marko Myllynen
Modified: 2016-12-20 13:46 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 13:46:50 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Marko Myllynen 2016-02-17 01:52:31 EST
Description of problem:
From PCPIntro(1):

       -S starttime
              By default the time window commences  immediately  in  real-time
              mode, or coincides with time at the start of the PCP archive log
              in archive mode.  The -S option may be used to specify  a  later
              time for the start of the time window.

                     To  specify an offset from the current time (in real-time
                     mode) or the beginning of a PCP archive (in archive mode)
                     simply specify the interval of time as the argument.  For
                     example -S 30min will set the start of the time window to
                     be  exactly  30  minutes  from  now in real-time mode, or
                     exactly 30 minutes from the start of a PCP archive.


$ pmval -S 1m kernel.all.sysfork
pmval: time window options are supported for archives only
Usage: pmval [options] metricname

So the man page and the libpcp code are not in sync.
Comment 1 Nathan Scott 2016-02-17 16:27:34 EST
This is a bit of a shortcoming (incorrect assumption) in the pmGetOptions(3) routine - should not be very hard to fix if someone wants to take a crack at it.
Comment 2 Fedora End Of Life 2016-11-24 10:36:30 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 3 Fedora End Of Life 2016-12-20 13:46:50 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.