Bug 156413 - xfs starts too early
xfs starts too early
Product: Fedora
Classification: Fedora
Component: xorg-x11 (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: X/OpenGL Maintenance List
David Lawrence
Depends On:
Blocks: FC4Blocker
  Show dependency treegraph
Reported: 2005-04-29 17:11 EDT by Bill Nottingham
Modified: 2014-03-16 22:53 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-03 03:51:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bill Nottingham 2005-04-29 17:11:19 EDT
Description of problem:

It starts at priority 8, which means it will fail with nfs-mounted /usr

Version-Release number of selected component (if applicable):


How reproducible:

Every time
Comment 1 Mike A. Harris 2005-04-30 13:51:41 EDT
reverted in 6.8.2-30 in dist-fc4-HEAD

How did rhgb ever work on systems that have /usr nfs mounted?
Comment 2 Mike A. Harris 2005-04-30 13:52:31 EDT
(meaning the X server binary is in /usr, so unavailable until NFS is mounted
 on such systems)
Comment 3 Ray Strode [halfline] 2005-05-02 09:02:22 EDT
It tries to start rhgb twice.   Once before network filesystems are mounted,
once after.
Comment 4 Ray Strode [halfline] 2005-05-02 09:04:25 EDT
An alternative to changing the default priority of xfs is to do
/sbin/service xfs start inside rc.sysinit or the gdm-early-login script,
although that seems icky.
Comment 5 Bill Nottingham 2005-05-02 12:03:20 EDT
Basically, rhgb silently failed with nfs /usr - you just didn't get it.

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