From owner-freebsd-net@FreeBSD.ORG Mon Apr 4 02:00:16 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB126106566B; Mon, 4 Apr 2011 02:00:16 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 3B5178FC08; Mon, 4 Apr 2011 02:00:15 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAIAlmU2DaFvO/2dsb2JhbACESKIJiHmnC48zgSiDTHcEjSM X-IronPort-AV: E=Sophos;i="4.63,294,1299474000"; d="scan'208";a="116949984" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 03 Apr 2011 22:00:10 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 35740B3FB0; Sun, 3 Apr 2011 22:00:10 -0400 (EDT) Date: Sun, 3 Apr 2011 22:00:10 -0400 (EDT) From: Rick Macklem To: "Marc G. Fournier" Message-ID: <1011733876.2669273.1301882410156.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE7 (Win)/6.0.10_GA_2692) Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: Re: nfs error: No route to host when starting apache ... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2011 02:00:16 -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 ... :( > Oops, sorry. The option is called "nolockd". rick