On Mon, Jun 08, 2015 at 10:33:22AM -0400, Sean Elble wrote: > On 08.06.2015 10:27, Chuck Lever wrote: > >>I don’t understand the need to “turn off” an address family. > >>That’s what > >>/etc/netconfig is supposed to be for. What’s not happening here that > >>should be? > > > >What I mean is: I’d rather not add more command line options if there > >is a way for rpc.nfsd to automatically and quietly do what is needed. > >But I don’t understand the use case here. Sean, can you explain it > >for > >bears of little brain? > > Sure, and please correct me if any of my understanding is incorrect > (as it may well be). In my environment, I wanted to have NFS only > listen on one interface of a multihomed host. In using the "--host" > parameter to do so, I saw the error message regarding IPv6 thrown. > While disabling IPv6 globally in /etc/netconfig is an option (one I > understand to be "global", in that it'd affect *all* applications on > the host), it'd be nice to disable IPv6 for a single service/daemon > instead. But doesn't something like rpc.nfsd --host 10.0.0.1 --no-ipv6 seem a bit redundant? I mean, you've already told it to listen to that one (ipv4) address. That'd argue for just disabling the warning in this case, I think. But my understanding of IPv6 is still poor. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
