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.
Description of problem:
The eBPF tools 'runqslower' and 'solisten' need man pages. All other tools in /usr/share/bcc/ have a man page.
Version-Release number of selected component (if applicable):
bcc-0.7.0-3.el8
bcc-tools-0.7.0-3.el8
Steps to Reproduce:
Install bcc & bcc-tools
# man runqslower
# man solisten
Actual results:
man pages do not exist
Expected results:
man page with detailed tool description/usage should be available
(In reply to Jean-Tsung Hsiao from comment #4)
> Missing man page for runqslower:
>
> [root@netqe24 ~]# rpm -qa | grep bcc
> bcc-0.11.0-1.el8.x86_64
> bcc-tools-0.11.0-1.el8.x86_64
> python3-bcc-0.11.0-1.el8.x86_64
> [root@netqe24 ~]# man runqslower
> No manual entry for runqslower
> [root@netqe24 ~]# uname -r
> 4.18.0-159.el8.x86_64
> [root@netqe24 ~]#
The man pages of bcc tools are all prefixed by "bcc-" to avoid conflicts. It seems than mandb db allows to find some tool without that prefix, but not runqslower. I'm not sure how mandb works, I wonder if that's related to the fact that runqslower is called runqlat in the NAME section. Looks like runqslower man page has been copy-paste from the runqlat one and not entirely edited afterwards:
$ man bcc-runqslower
runqslower(8) System Manager's Manual runqslower(8)
NAME
runqlat - Trace long process scheduling delays.
SYNOPSIS
runqslower [-p PID] [min_us]
Anyway, that's an other issue and I'll open a new bz for that.
(In reply to Jean-Tsung Hsiao from comment #6)
> Can't pass "man runqslower":
>
> [root@netqe30 bpf]# man runqslower
> No manual entry for runqslower
See my previous comment.
(In reply to Jerome Marchand from comment #5)
> The man pages of bcc tools are all prefixed by "bcc-" to avoid conflicts. It
> seems than mandb db allows to find some tool without that prefix, but not
> runqslower. I'm not sure how mandb works, I wonder if that's related to the
> fact that runqslower is called runqlat in the NAME section. Looks like
> runqslower man page has been copy-paste from the runqlat one and not
> entirely edited afterwards:
>
> $ man bcc-runqslower
> runqslower(8)
> System Manager's Manual
> runqslower(8)
>
> NAME
> runqlat - Trace long process scheduling delays.
>
> SYNOPSIS
> runqslower [-p PID] [min_us]
>
> Anyway, that's an other issue and I'll open a new bz for that.
The fix has been verified:
[root@netqe10 ~]# man bcc-runqslower
runqslower(8) System Manager's Manual runqslower(8)
NAME
runqlat - Trace long process scheduling delays.
SYNOPSIS
runqslower [-p PID] [min_us]
DESCRIPTION
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:1594