[ILUG] Dapper won't mount NFS drives at boot

[Conor Wynne]

> Are the mounts specified in /etc/fstab as IP addresses or DNS names?
> 
> It's a problem I've been having with a sarge box and still 
> haven't sorted, despite the fact that named is set to come up 
> before NFS.

Yes, I had that issue too. I was sure that the init scripts were set in
the correct order, 
All the services (dependencies) were started fine too, yet fstab
wouldn't mount the nfs volumes. 

> Cian
> Niall O Broin wrote:
> > I have the NFS problem on several dapper NFS clients - they 
> will not 
> > mount NFS drives at startup. The NFS client packages are correctly 
> > installed, and the fstab is correctly configured, because 
> once the box 
> > is up, I can type
> >
> > mount /any_nfs_volume
> >
> > and off I go.
> >
> > It appears that the script  /etc/network/if-up.d/mountnfs  which 
> > SHOULD be doing this is simply not being called at startup. ls -lu 

Think I ended up going for autofs (my favorite little service) as this
did the job nicely. 
Logging in as a user would access the homedir, which would call nfs
mount anyway, so job done. 
Not that's what I used it for (or configured), but it should work,
shouldn't it?

Failing that, you could use /etc/rc.local (or whatever ununtu call it)
and 
Mount it automagically once all the other scripts are finished loading. 

It's a workaround if nothing else Niall.

Later,
Conor. 

I googled and rc.local is not in ubuntu (knew that) :
http://www.debian.org/doc/FAQ/ch-customizing.en.html

Quote "Enter the script foo into the directory /etc/init.d/
Run the Debian command update-rc.d with appropriate arguments, to set up
links 
between the (command-line-specified) directories rc?.d and
/etc/init.d/foo. 
Here, '?' is a number from 0 through 6 and corresponds to each of the
System V runlevels.
Reboot the system. "