freebsd stable - Jul 2017 - stable/11 r321349 crashing immediately

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.

IIRC, this was a fairly common practice with amd (and the like).
> ....
Peace,
david
-- 
David H. Wolfskill				david at catwhisker.org
What kind of "investigation" would it be if it didn't "follow
the money?"

See http://www.catwhisker.org/~david/publickey.gpg for my public key.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 603 bytes
Desc: not available
URL:
<http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20170722/d757205f/attachment.sig>

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.