Bug 449095 - include impending systemtap network client in default installation
Summary: include impending systemtap network client in default installation
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: distribution
Version: 5.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: RHEL Program Management
QA Contact: Daniel Riek
URL:
Whiteboard:
Depends On: 441859
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-30 12:10 UTC by Frank Ch. Eigler
Modified: 2011-11-02 21:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-02 21:36:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Frank Ch. Eigler 2008-05-30 12:10:10 UTC
The version of systemtap incoming for RHEL5.3 is going to have a
client/server feature that allows relatively "naked" machines
(those without an installed compiler, debuginfo, ...) to use a
a systemtap server on their local network to transparently
build systemtap modules for them.  Since this client will be very
small (a few kilobytes, no new dependencies AFAIK), and would
open up useful diagnostic capabilities, we should just install
it by default.

Comment 1 RHEL Program Management 2008-07-21 23:01:27 UTC
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".


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