Bug 88063 - request for netfs to start after ybind
request for netfs to start after ybind
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
9
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-04-04 22:04 EST by G Sandine
Modified: 2014-03-16 22:35 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-04-07 17:38:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description G Sandine 2003-04-04 22:04:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.3) Gecko/20030327
Debian/1.3-4

Description of problem:
We have many workstations that use hostname NFS mounts, with /etc/hosts
supplemented by NIS.  NFS hostname (rather than IP address) mounts fail when the
host IP address is provided by NIS, because netfs is linked at S25 while ypbind
is linked as S27.  We move rc?.d/S25netfs to rc?.d/S29netfs in all of our
workstations so we are free to move the NFS and NIS servers around and have host
to IP info coming from NIS and have successful NFS (hostname in fstab) mounts,
without having to update /etc/hosts in every client.

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

How reproducible:
Always

Steps to Reproduce:
1. Put hostname NFS mount entries in /etc/fstab for a client, without specifying
host to IP map in the client's hosts file.
2. Make portmap, nfslock, netfs, and ypbind start at boot.
    

Actual Results:  NFS mounts are attempted prior to starting ypbind, and they
fail due to inability to locate host (by name).

Expected Results:  This should work, rather than having to resort to DNS or to
manually update hosts file in multiple clients.

Additional info:

Suggested fix is to link netfs to S2x (x > 5), so it comes after S25, which
links to ypbind.
Comment 1 G Sandine 2003-04-04 22:08:18 EST
Braino in the additional subject -- we would like netfs to start _after_ ypbind.
Comment 2 Bill Nottingham 2003-04-07 17:26:19 EDT
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.
Comment 3 G Sandine 2003-04-07 17:38:20 EDT
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.

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