Bug 11992

Summary:	should packages depend on xinetd!?
Product:	[Retired] Red Hat Raw Hide	Reporter:	Michael Tokarev <mjt>
Component:	xinetd	Assignee:	Trond Eivind Glomsrxd <teg>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-06-08 18:44:20 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:

Description Michael Tokarev 2000-06-08 18:44:19 UTC

This is not really a bug in xinetd itself.
RH seemed to switch from inted to xinetd now,
and made some updates to other packages to include
dependance of xnietd.  I will consider it a bug, since
there is no bad things in just adding file to /etc/xinetd.d,
and not requiring xinetd itself.  Why place additional dependance?
I want to use old-good inetd (that is owned by redhat now,
and should be forget?), but any new package I install requires
to install xinetd from me.  Not good.

Comment 1 Trond Eivind Glomsrxd 2000-06-08 18:48:12 UTC

I am planning of removing those, but inetd will not be included with or
supported with our next release. And if those packages are to be useful, and not
just wasted disk space, xinetd.d is required in the distribution setting.