NFS won't mount at boot

[Gavin McDonald]

I apologise for the waste of bandwidth;

The answer, for any interested parties, is:

# vi /etc/init.d/ypbind
change 
  # chkconfig: - 27 73
to
  # chkconfig: - 23 77
then
# chkconfig --del ypbind
# chkconfig --add ypbind
# chkconfig --level 345 ypbind on

-G

Regards,

Gavin McDonald
========================
EVI Logistic Enterprises
email: me at gavitron.com
phone: (604) 313-3845



> -----Original Message-----
> From: Gavin McDonald [mailto:gavitron at gmail.com]
> Sent: Thursday, April 20, 2006 6:45 PM
> To: 'General Red Hat Linux discussion list'
> Subject: RE: NFS won't mount at boot
> 
> Ok, in a classic keyboard-before-brain scenario, I neglected to do a
> simple scan of the boot logs;
> 
> Doing so almost certainly points to the boot order, bringing up NFS before
> NIS, (and the NAS authenticates via NIS...)
> 
> So to rephrase my earlier post,
> 
> "How do I use chkconfig to start NIS _before_ NFS?"
> 
> -G
> 
> 
> 
> Regards,
> 
> Gavin McDonald
> ========================
> EVI Logistic Enterprises
> email: me at gavitron.com
> phone: (604) 313-3845
> 
> 
> 
> > -----Original Message-----
> > From: Gavin McDonald [mailto:gavitron at gmail.com]
> > Sent: Thursday, April 20, 2006 6:21 PM
> > To: 'General Red Hat Linux discussion list'
> > Subject: NFS won't mount at boot
> >
> > Hi,
> >
> > This may have been asked before, But I can't seem to find the answer by
> > google, or my list archives;
> >
> > I have many RHEL3 machines, each with three NFS mounts from a NAS
> device.
> > Each machine gets a few identical lines added to /etc/fstab, and they
> all
> > mount the network drives at boot, as expected.  On a batch of machines I
> > am building right now, (Same version of RHEL, same /etc/fstab,)  the NFS
> > mounts wont come up at boot, but a 'mount -a' anytime after boot brings
> > the drives up immediately.
> >
> > I have the NAS device declared in /etc/hosts, and I reference it by name
> > in /etc/fstab.  /etc/nsswitch contains "hosts: files nis dns" too, yet
> > this still smells like a name resolution problem.  Have I missed
> anything?
> >
> > I have vague recollections of a fix to this that involved changing
> > /etc/rc.d/S files, but I am at a loss to remember, or even locate such a
> > thing.  Maybe I remember incorrectly...?
> >
> > Regards,
> >
> > Gavin McDonald
> > ========================
> > EVI Logistic Enterprises
> > email: me at gavitron.com
> > phone: (604) 313-3845
> >