Date: Sat, 20 May 2006 12:57:57 -0700 From: "Kip Macy" <kip.macy@gmail.com> To: babkin@users.sourceforge.net Cc: freebsd-hackers@freebsd.org, Steven Hartland <killing@multiplay.co.uk> Subject: Re: Re: NFS server not responding prevents boot Message-ID: <b1fa29170605201257u79078258xb2f8be1219e91de6@mail.gmail.com> In-Reply-To: <18923565.8854391148037026048.JavaMail.root@vms168.mailsrvcs.net> References: <18923565.8854391148037026048.JavaMail.root@vms168.mailsrvcs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Uhhhhm that is what intr is for - and it won't cause silent data loss. -Kip On 5/19/06, Sergey Babkin <babkin@verizon.net> wrote: > >From: Steven Hartland <killing@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=3D"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 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b1fa29170605201257u79078258xb2f8be1219e91de6>