Bug 175161 - rhgb started before /usr/lib mounted
Summary: rhgb started before /usr/lib mounted
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-12-07 01:20 UTC by n0dalus
Modified: 2014-03-17 02:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-12-07 15:03:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description n0dalus 2005-12-07 01:20:01 UTC
Description of problem:
Currently rc.sysinit checks for the presence of /usr/bin/rhgb, but not it's
required libraries in /usr/lib. If /usr/lib is a separate partition, but
/usr/bin is not, this causes rhgb to fail and lots of calls to rhgb-client to fail.

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

Files containing problems:
/etc/rc.d/rc.sysinit
/etc/rc.d/rc
/etc/init.d/functions

Actual results:
rhgb fails, lots of error messages like: /usr/bin/rhgb-client: error while
loading shared libraries: libglib-2.0.so.0: cannot open shared object file: No
such file or directory

Expected results:
If possible, rc.sysinit and the other scripts should check to see that /usr/lib
is mounted when checking to see if /usr/bin/rhgb* exists and before trying to
run them. Later in rc.sysinit there is a bit of code to re-attempt the running
of rhgb.
At the very least, the failure to start rhgb should be noted and the scripts
should be able to avoid most of the subsequent error messages.

Additional info:
I realize that have a separate partition for /usr/lib is probably unusual, but
it would still be nice to see this fixed.

Comment 1 Bill Nottingham 2005-12-07 15:03:36 UTC
/usr/bin and /usr/lib really need to be on the same partition; I don't think
otherwise is supported in many areas, not just in rhgb.


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