Bug 449095

Summary:	include impending systemtap network client in default installation
Product:	Red Hat Enterprise Linux 5	Reporter:	Frank Ch. Eigler <fche>
Component:	distribution	Assignee:	RHEL Program Management <pm-rhel>
Status:	CLOSED WONTFIX	QA Contact:	Daniel Riek <riek>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.2	CC:	ananth, brolley, ebachalo
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-02 21:36:33 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	441859
Bug Blocks:

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 "?".