Red Hat Bugzilla – Bug 68462
netfs starts to early
Last modified: 2014-03-16 22:28:44 EDT
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
Created attachment 64584 [details]
Patch: Update chkconfig info so that netfs starts after ypbind
ypbind requires things in /usr. /usr could be on nfs.
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.)
Resolving as deferred; there are some ways to possibly do this, but they'd rely
on doing things other than just tweaking the priorities.