Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 860352[details]
Trivial python implementation of uptime(1) using PCP
Description of problem:
The pmCtime and pmLocaltime interfaces in libpcp are incorrectly called
in the python wrapper module, making these two interfaces unusable. An
oversight in the testing scripts meant these went undetected until now.
These routines are useful for reporting timestamps from sampled data.
Version-Release number of selected component (if applicable):
pcp-3.8.10-4
How reproducible:
Every time.
Steps to Reproduce:
1.Run the attached uptime.py program, a trivial python uptime(1) tool
2.
3.
Actual results:
Script fails with a backtrace at the call to context.pmLocaltime()
Expected results:
Script should produce the same output as /usr/bin/uptime when doing
live-mode sampling (which it does by default), as in...
$ ~/uptime.py && uptime
11:53:09 up 3 days, 20:20, 15 users, load average: 1.92, 1.84, 1.51
11:53:09 up 3 days, 20:20, 15 users, load average: 1.92, 1.84, 1.51
Additional info:
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Created attachment 860352 [details] Trivial python implementation of uptime(1) using PCP Description of problem: The pmCtime and pmLocaltime interfaces in libpcp are incorrectly called in the python wrapper module, making these two interfaces unusable. An oversight in the testing scripts meant these went undetected until now. These routines are useful for reporting timestamps from sampled data. Version-Release number of selected component (if applicable): pcp-3.8.10-4 How reproducible: Every time. Steps to Reproduce: 1.Run the attached uptime.py program, a trivial python uptime(1) tool 2. 3. Actual results: Script fails with a backtrace at the call to context.pmLocaltime() Expected results: Script should produce the same output as /usr/bin/uptime when doing live-mode sampling (which it does by default), as in... $ ~/uptime.py && uptime 11:53:09 up 3 days, 20:20, 15 users, load average: 1.92, 1.84, 1.51 11:53:09 up 3 days, 20:20, 15 users, load average: 1.92, 1.84, 1.51 Additional info: