On Jun 8, 2015, at 10:33 AM, Sean Elble <elbles@xxxxxxxxxx> 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. OK, yes I read that last week, and had just forgotten it. That sounds to me like - - host is broken (or, at least noisier than it should be in this case). Do you provide an IP address or a hostname when specifying - - host? > 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. > > Of course, the fact that at least Ubuntu and RHEL (and almost certainly their upstream and their derivatives, respectively) relay the error message when running the NFS init scripts could confuse someone into thinking NFS failed to start properly (until they look at the output of netstat -nalp, etc.). I'd almost argue that's a larger concern. By the same token, "--host" seems a little used option, for whatever reason. > > In any case, I'm the little brained one in this group. :-) -- Chuck Lever chucklever@xxxxxxxxx -- 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
