Bug 88063
Summary: | request for netfs to start after ybind | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | G Sandine <bugzilla> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-04-07 21:38:20 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
G Sandine
2003-04-05 03:04:08 UTC
Braino in the additional subject -- we would like netfs to start _after_ ypbind. The issue here is that currently the ypbind init script relies on programs in /usr, which could be mounted via NFS, which leads to circular dependencies. Right, I did not think about that. We'll just swap netfs and ypbind starts and stops here since it works better for us that way. Perhaps start ypbind in the netfs initscript (only if necessary and possible [i.e. /usr is available] -- I'm not sure how to check the "necessary" part), then exit the ypbind initscript straightaway if ypbind is already running. It's awfully convenient for us to be able to move around the NFS and NIS servers without having to update local host tables. Actually, it seems resorting to (local) DNS would be better than hacking on initscripts. Thank you. |