From owner-freebsd-hackers@FreeBSD.ORG  Sat May 20 19:58:00 2006
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
X-Original-To: freebsd-hackers@freebsd.org
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0EF5316A457
	for <freebsd-hackers@freebsd.org>; Sat, 20 May 2006 19:58:00 +0000 (UTC)
	(envelope-from kip.macy@gmail.com)
Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.192])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 76AA843D55
	for <freebsd-hackers@freebsd.org>; Sat, 20 May 2006 19:57:58 +0000 (GMT)
	(envelope-from kip.macy@gmail.com)
Received: by wx-out-0102.google.com with SMTP id i31so700506wxd
	for <freebsd-hackers@freebsd.org>; Sat, 20 May 2006 12:57:57 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=cWKq/PJpm3tFYQdEl8CttY0+jbb9R3KvB7yujMrhF7B57pWPrBI5cB6nHOdx12P5yPl5TNjABKN1z2SHQx7gGJboI5IxCuE0FwPzErSuXtku5Qr2vLBbe1LIcAFKd0wyI7yyMva9pi7OD5sNWjALP+zwndJgWvIalg5VKfviZZc=
Received: by 10.70.59.13 with SMTP id h13mr3541187wxa;
	Sat, 20 May 2006 12:57:57 -0700 (PDT)
Received: by 10.70.71.2 with HTTP; Sat, 20 May 2006 12:57:57 -0700 (PDT)
Message-ID: <b1fa29170605201257u79078258xb2f8be1219e91de6@mail.gmail.com>
Date: Sat, 20 May 2006 12:57:57 -0700
From: "Kip Macy" <kip.macy@gmail.com>
To: babkin@users.sourceforge.net
In-Reply-To: <18923565.8854391148037026048.JavaMail.root@vms168.mailsrvcs.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <18923565.8854391148037026048.JavaMail.root@vms168.mailsrvcs.net>
Cc: freebsd-hackers@freebsd.org, Steven Hartland <killing@multiplay.co.uk>
Subject: Re: Re: NFS server not responding prevents boot
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: kmacy@fsmware.com
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 20 May 2006 19:58:00 -0000

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=
"
>