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:
We were asked to review Developers' Guide for the RHEL6.1, this bug comes from
the effort:
One of the important features of new RHEL6.1 systemtap is the --remote option, allowing to build the systemtap module locally, and execute remotely via SSH:
--remote [USER@]HOSTNAME
Set the execution target to the specified ssh
host, optionally using a username not matching
your own. This option may be repeated to target
multiple execution targets. Passes 1-4 are com-
pleted locally as normal to build the script, and
then pass 5 will copy the module to the target and
run it. (EXPERIMENTAL)
As the Dev Guide describes important features brought in RHEL6.0, short mention of this new feature should probably be added.
Description of problem: We were asked to review Developers' Guide for the RHEL6.1, this bug comes from the effort: One of the important features of new RHEL6.1 systemtap is the --remote option, allowing to build the systemtap module locally, and execute remotely via SSH: --remote [USER@]HOSTNAME Set the execution target to the specified ssh host, optionally using a username not matching your own. This option may be repeated to target multiple execution targets. Passes 1-4 are com- pleted locally as normal to build the script, and then pass 5 will copy the module to the target and run it. (EXPERIMENTAL) As the Dev Guide describes important features brought in RHEL6.0, short mention of this new feature should probably be added.