Uhhhhm that is what intr is for - and it won't cause silent data loss.
-Kip
On 5/19/06, Sergey Babkin <bab...@verizon.net> wrote:
From: Steven Hartland <kill...@multiplay.co.uk>
Anyway the big question is how can I change all our NFS
mounts so that failed mounts dont prevent the machines
booting to the point where they can be fixed remotely
i.e. have started sshd.
Doh!! spent ages googling for the answer then found it
in 2mins of looking through the man pages.
The option for anyone interested is "bg" for -b from
the command line to mount:
[quote="man mount_nfs"]
-b
If an initial attempt to contact the server fails, fork off a
I usually use "soft,bg". The "soft" option makes the
operations on this filesystem fail if the server
is not available instead of hanging (unkillable!)
forever and waiting for the server to come up.
-SB
7 messages in org.freebsd.freebsd-hackersNFS server not responding prevents boot