Bug 68462 - netfs starts to early
Summary: netfs starts to early
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-10 12:14 UTC by Toralf
Modified: 2014-03-17 02:28 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-08-28 08:29:36 UTC
Embargoed:


Attachments (Terms of Use)
Patch: Update chkconfig info so that netfs starts after ypbind (422 bytes, patch)
2002-07-10 12:16 UTC, Toralf
no flags Details | Diff

Description Toralf 2002-07-10 12:14:46 UTC
Description of Problem:
The netfs init script has startup sequence number 25. This is somewhat too low
as it means that ypbind has number 27. In other words, netfs will be started
before ypbind, which means that it fails if NIS is used for host name resolution.


Version-Release number of selected component (if applicable):
6.40-1, 6.53-1, 6.67-1

Comment 1 Toralf 2002-07-10 12:16:17 UTC
Created attachment 64584 [details]
Patch: Update chkconfig info so that netfs starts after ypbind

Comment 2 Bill Nottingham 2002-08-14 02:00:22 UTC
ypbind requires things in /usr. /usr could be on nfs.

Comment 3 Toralf 2002-08-28 08:29:29 UTC
Yes, never really though of that. Using NIS for host names still seems more
likely, but perhaps only from where I'm standing.

An unresolvable race, I guess, unless you break with the strict ordered service
startup and actually try to start ypbind several times (and silently ignore
failures of initial attempts.)

Comment 4 Bill Nottingham 2002-08-28 16:10:07 UTC
Resolving as deferred; there are some ways to possibly do this, but they'd rely
on doing things other than just tweaking the priorities.


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