Date: Wed, 26 Jul 2017 00:19:12 +0000 (UTC) From: "G. Paul Ziemba" <pz-freebsd-stable@ziemba.us> To: freebsd-stable@FreeBSD.org Subject: Re: stable/11 r321349 crashing immediately Message-ID: <ol8n60$khu$1@usenet.ziemba.us> References: <201707222016.v6MKGMPa070777@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
truckman@freebsd.org (Don Lewis) writes:
>On 22 Jul, David Wolfskill wrote:
>> 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.
Yes, I've been running amd for years, but the warning in the amd(8)
man page prompted me to switch to autofs last week as part of updating
my system. My amd maps had a way of specifying per-client information,
which I indeed used in the way indicated above.
I bit the bullet yesterday and implemented this capability in an
include_nis script attached to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221010
It currently doesn't notice IPv6 addresses that belong to "self,"
as I haven't decided how to parse _that_ ifconfig output (and does
anyone really specify IPv6 addresses in NIS maps?)
--
G. Paul Ziemba
FreeBSD unix:
5:16PM up 18:11, 8 users, load averages: 0.36, 0.32, 0.33
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ol8n60$khu$1>