Re: rpcbind -h

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Nov 7, 2011, at 12:21 PM, Jim Rees wrote:

> Chuck Lever wrote:
> 
>  On Nov 6, 2011, at 10:58 AM, Jim Rees wrote:
> 
>> Is there some good reason why the rpcbind '-h' option (bind to given
>> address) applies only to the udp listening socket and not to the tcp socket?
> 
>  Yes.  See the mail archives.  I believe we've discussed this thoroughly
>  within the past six months to a year.  If there's any bug here, it's that
>  "-h" is not well documented.
> 
> It's documented well enough but I'm still in the dark about the reason.  I
> don't recall the discussion and can't find it in the archives.  The search
> box on spinics isn't working for me, it returns results from the entire web,
> not just the list archive.
> 
> As I said before, I was hoping for the equivalent of "portmap -l".  I was
> ready to code up a patch of some kind but now have a workaround (mount with
> nolock and don't run rpcbind at all).

I wouldn't object to having a "local only" option that turns off the AF_INET[6] listener and just listens on the AF_LOCAL socket, but that may be problematic until we have a complete transition away from glibc RPC, which still uses AF_INET loopback extensively.

Glad you found a work-around.

-- 
Chuck Lever
chuck[dot]lever[at]oracle[dot]com




--
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


[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux