NFS problem

[Tim]

On Thu, 2005-11-24 at 22:43 +0100, Eric TANGUY wrote:
> I have a fc3 server and fc4 clients. Each client mount 2 nfs directory
> at bootup :
> 192.168.10.10:/home       /home       nfs  exec,dev,suid,rw 1 1
> 192.168.10.10:/usr/local  /usr/local  nfs  exec,dev,suid,ro 1 1
>
> Since today /home is not mounted at boot (but /usr/local is mounted)
> but this seems to be randomly.

Seems some unusual options.  If I were doing the same thing, mine would
be something like:

192.168.10.10:/home       /home       nfs  auto,noexec,nodev,intr,udp
192.168.10.10:/usr/local  /usr/local  nfs  auto,nodev,intr,udp,ro

Although the "defaults" set "auto" and "rw", and other things, I like to
see what options I've set.  I have to read the man files to find out
what the defaults are.

The "exec" and "dev" options would be unusual for home space, if not
actually risky, I can't see why you'd want dev for /usr/local, either.  

And the "1 1" checking options don't seem sensible across a network, let
the machine with the drive do that.  Perhaps they're something to do
with the problems you're having (it not being able to fsck something on
a remote system).

-- 
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.