Bug 24196

Summary:	"xfs" installed and started even with no X installed
Product:	[Retired] Red Hat Linux	Reporter:	Chris Adams <linux>
Component:	XFree86	Assignee:	Mike A. Harris <mharris>
Status:	CLOSED RAWHIDE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:	Florence Gold
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-01-20 19:24:32 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 Chris Adams 2001-01-17 04:55:05 UTC

I did a minimal "Custom" install (basically for a home gateway router) with
very little installed (no X at all).  However, xfs was still installed and
started automatically at boot.  If X is not installed, xfs should not be
installed or started by default.

Comment 1 Glen Foster 2001-01-17 18:20:44 UTC

This defect is considered MUST-FIX for Florence Gold release

Comment 2 Mike A. Harris 2001-01-20 08:41:12 UTC

xfs is *not* dependant on XFree86 being installed.  xfs can be installed
on a machine on a network and used simply as a networked font server without
having XFree86 installed.  The XFree86-xfs package is required however by
the packages chkfontpath, kdebase, Xconfigurator, and XFree86 itself,
and I believe possibly by other packages also.  If you have elected to
install any of the above mentioned packages, they will drag in xfs as
it is needed (or something included in it is needed) for proper operation
of the above packages.  If you do not need xfs, and do not need the above
listed packages either, then make sure you unselect them and any other
dependant packages during the custom install, and do not choose
"automatically install all dependancies".

I will look into why xfs service is being started at boot even if it
isn't required though, as that sounds like a reasonable concern indeed.

Comment 3 Chris Adams 2001-01-20 19:24:29 UTC

Okay, it appears that Xfree86-xfs was installed because I selected
"Printer Support".  I have a PostScript printer, so I don't need
Ghostscript, but rhs-printfilters pulls in ghostscript, which pulls in
Xfree86-libs, several font packages, chkfontpath, and XFree86-xfs.

The only way I can think of to not have xfs start at boot in this setup
would be to have the XFree86-xfs package not install it as starting by
default.  Then have the XFree86 package "chkconfig xfs on", but that
would require that XFree86-xfs package be installed before XFree86.

I still miss the feature of older Red Hat installers that allowed you to
select the services to start at boot during configuration.  Any chance
of bringing this back?  Maybe service configuration could be in a
section of the RPM file and the comps file, so it could be done before
install.

Comment 4 Mike A. Harris 2001-01-28 09:02:17 UTC

Fixed in Rawhide.  xfs will check for the existance of an X server
installation during initscript processing.  If no X server is installed,
xfs will not start.