Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1636

Summary: xfs in runlevel 3?
Product: [Retired] Red Hat Linux Reporter: Peter Jones <pjones>
Component: XFree86Assignee: Cristian Gafton <gafton>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-03-22 21:24:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Peter Jones 1999-03-20 01:35:14 UTC
Running xfs in runlevel 3 makes no sense.  startx probably
needs to know how to start and stop it instead.

Comment 1 Preston Brown 1999-03-22 21:24:59 UTC
The developers slightly disagree.  There are many many ways to start X
-- startx is only one of them.  Some sites use scripts that give their
own parameters to xinit, others use xdm, kdm, or gdm.  The
possibilities are wide.

While it is true that xfs is only useful while X is running in MOST
cases, it can also be used as a networked font server, so in other
cases running it while X isn't running on the local console DOES make
sense.  Finally, in Red Hat Linux 6.0, some sort of display manager
will be the default way to log into X, in which case X will be running
99% of the time.  If your machine doesn't fall into any of these
categories, it is a simple matter to do a 'chkconfig --del xfs' to
turn off xfs permanently from the runlevel, and then use
/etc/rc.d/init.d/xfs (start|stop) to turn it on and off manually.