On Thu, Aug 30, 2007 at 04:50:51PM +0200, Eric Noulard wrote: > I've updated the bug. > I think I found the reason. > > We are linked again glibc ONC-RPC whereas we may/should link > against tirpc. The libs have the same name isn't it? Are they binary compatible? If not, shouldn't this be implemented as a new command transport layer (a la xmlrpc)?
Frederik > This may need more work than that we'll see that issue later. > In the meantime one should launch rpcbind using -i option. > > 2007/8/30, Eric Noulard <[EMAIL PROTECTED]>: > > I have a weird behavior of > > TSP and in particular the rpcbind daemon o a Fedora 7 (i386) > > https://savannah.nongnu.org/bugs/index.php?20936 > > > > I suspect a bug either in rpcbind daemon itself or > > in the rpc lib embedded in glibc 2.6 > > > > rpcbind is version 0.1.4-6.fc7 > > glibc is version 2.6-4 > > > > Can any of you test on your box if you have such a problem? > > > > It seems that, at least on FC6 box, rpcbind is not used but > > a portmap-4.0 is used instead? > > > > -- > > Erk > > > > > -- > Erk > > > _______________________________________________ > Tsp-devel mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/tsp-devel > _______________________________________________ Tsp-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/tsp-devel
