From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616 Description of problem: The problem occurs in FC1 as well. By default there is following order in initscripts: S25netfs, S27ypbind. Therefore if in /etc/fstab hostname is used insted of IP address (e.g. nfsserv:/home /home nfs auto...), and the hostname is resolvable only through NIS, netfs script will fail to mount these filesystems. Version-Release number of selected component (if applicable): ypbind-1.17.2-1 How reproducible: Always Steps to Reproduce: 1.Reboot ;) 2. 3. Additional info:
see also bug 52006 This still applies to the latest devel tree, but I lack privileges necessary to modify the Version field.
Created attachment 109747 [details] Move ypbind init from 27 to 24, directly before netfs (25) This is untested. I have no idea how this change in magic numbers may or may not break the arcane boot process that is SysVinit.
*** Bug 52006 has been marked as a duplicate of this bug. ***
I've modified the ypbind init script priorities in RHEL-3 & FC-3 & FC-2 to S24 & K76 from S27 & K73. The fix is in the following RPMS. FC-3: 1.17.2-7 FC-2: 1.17.2-6 RHEL-3: 1.12-5.21.4
Long been fixed. Closing bug appropriately.