On 04/13/2011 11:32 PM, Ben Hutchings wrote: > On Wed, Apr 13, 2011 at 11:01:26PM +0200, Luk Claes wrote: >> On 04/13/2011 10:39 PM, Andrew O. Shadoura wrote: > [...] >>> It could be replaced by rpcinfo (as suggested before) which is provided >>> by libc-bin, so no extra dependencies and no breakage. Why not? Why >>> such a resistance? >> >> I didn't see the suggestion to use rpcinfo. The one of libc-bin will >> probably be removed at some point, though we always will have the one of >> rpcbind. >> >> Committed, so will be in a new upload unless any objections are out. > > Does glibc's rpcinfo actually work with rpcbind, then? It is > documented as only speaking the portmapper protocol, and we now > know libtirpc doesn't handle that.
Yes, it does work. > Also, I think either method (/dev/tcp/localhost/111 or rpcinfo) > will not work for anyone who configures rpcbind to listen on IPv6 > only. Only rpcbind's rpcinfo would work in that case, true. Cheers Luk -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
