From owner-freebsd-questions@FreeBSD.ORG Sun Apr 3 04:35:22 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43987106566C; Sun, 3 Apr 2011 04:35:22 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.freebsd.org (Postfix) with ESMTP id 125D18FC08; Sun, 3 Apr 2011 04:35:21 +0000 (UTC) Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by hub.org (Postfix) with ESMTP id D32923250A8D; Sun, 3 Apr 2011 01:35:19 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 47881-04; Sun, 3 Apr 2011 04:35:12 +0000 (UTC) Received: by hub.org (Postfix, from userid 1002) id F37713250A8B; Sun, 3 Apr 2011 01:35:11 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by hub.org (Postfix) with ESMTP id E91003250A7E; Sun, 3 Apr 2011 01:35:11 -0300 (ADT) Date: Sun, 3 Apr 2011 01:35:11 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@hub.org To: Rick Macklem In-Reply-To: <326244177.2606708.1301701360593.JavaMail.root@erie.cs.uoguelph.ca> Message-ID: References: <326244177.2606708.1301701360593.JavaMail.root@erie.cs.uoguelph.ca> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org, "Marc G. Fournier" Subject: Re: nfs error: No route to host when starting apache ... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Apr 2011 04:35:22 -0000 On Fri, 1 Apr 2011, Rick Macklem wrote: >> Since rpc.lockd and rpc.statd expect to be able to do IP broadcast >> (same goes for rpcbind), I suspect that might be a problem w.r.t. >> jails, although I know nothing about how jails work? >> > Oh, and you can use the "nolock" mount option to avoid use of > rpc.lockd and rpc.statd. based on the mount_nfs man page, as well as trying it just in case, this option no longer appears to be availalble in the 7.x nfs code ... :(