From owner-freebsd-stable@freebsd.org Sat Jul 22 20:16:36 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85BC6DAC501 for ; Sat, 22 Jul 2017 20:16:36 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 65D3964318 for ; Sat, 22 Jul 2017 20:16:36 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id v6MKGMPa070777; Sat, 22 Jul 2017 13:16:26 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201707222016.v6MKGMPa070777@gw.catspoiler.org> Date: Sat, 22 Jul 2017 13:16:22 -0700 (PDT) From: Don Lewis Subject: Re: stable/11 r321349 crashing immediately To: david@catwhisker.org cc: unp@ziemba.us, freebsd-stable@FreeBSD.org In-Reply-To: <20170722160233.GY20018@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jul 2017 20:16:36 -0000 On 22 Jul, David Wolfskill wrote: > On Fri, Jul 21, 2017 at 04:53:18AM +0000, G. Paul Ziemba wrote: >> ... >> >It looks like you are trying to execute a program from an NFS file >> >system that is exported by the same host. This isn't exactly optimal >> >... >> >> Perhaps not optimal for the implementation, but I think it's a >> common NFS scenario: define a set of NFS-provided paths for files >> and use those path names on all hosts, regardless of whether they >> happen to be serving the files in question or merely clients. > > Back when I was doing sysadmin stuff for a group of engineers, my > usual approach for that sort of thing was to use amd (this was late > 1990s - 2001) to have maps so it would set up NFS mounts if the > file system being served was from a different host (from the one > running amd), but instantiating a symlink instead if the file system > resided on the current host. Same here. It's a bit messy to do this manually, but you could either use a symlink or a nullfs mount for the filesystems that are local.