Date: Sat, 22 Jul 2017 13:16:22 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: david@catwhisker.org Cc: unp@ziemba.us, freebsd-stable@FreeBSD.org Subject: Re: stable/11 r321349 crashing immediately Message-ID: <201707222016.v6MKGMPa070777@gw.catspoiler.org> In-Reply-To: <20170722160233.GY20018@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201707222016.v6MKGMPa070777>