Red Hat Bugzilla – Bug 169036
ypbind starts too late in the boot sequence (needs to be before netfs)
Last modified: 2009-02-24 18:02:36 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050909 Red Hat/1.7.10-1.4.2
Description of problem:
The rc*.d links to /etc/init.d/ypbind are out of sequence.
For hosts that mount NFS file systems that reside on a server which is only resolvable through NIS, ypbind must start before netfs.
The symptom is that some NFS file systems were not mounting during boot but could be mounted with no problems with 'mount -a' after the system was fully booted.
The fix is to renumber the symlinks for ypbind in /etc/rc*.d to be before netfs. On a stock RHEL4 system, the links are S27ypbind which follows S25netfs in the boot process. If ypbind links are renamed S23ypbind, all NFS file systems mount correctly at boot time.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. /etc/fstab has an nfs mount whose server name is only resolvable by NIS
2. boot or reboot
Actual Results: NFS file system does not mount during boot.
Following boot, mount -a will correctly mount the file system.
Expected Results: All NFS file systems should mount during boot.
To fix this on our systems, after a clean RHEL4 install, we run:
cp /etc/init.d/ypbind /etc/init.d/ypbind.orig
chkconfig --del ypbind
sed 's/# chkconfig: - 27 73/# chkconfig: - 23 77/' /etc/init.d/ypbind.orig \
chkconfig --add ypbind
chkconfig --level 345 ypbind
Ideally, S23 or S23 (or anything appropriate and before netfs) should be the RHEL default start order for ypbind so we don't have to apply this workaround after each install.
Is this still an issue? It's very difficult to change service start ordering in the middle of a release. We may need to move this to RHEL6.
Closing as there hasn't been any update in years.