On Fri, 17 Sep 2010, Chuck Lever wrote: > > On Sep 17, 2010, at 2:12 PM, Jan Rękorajski wrote: > > > Hi, > > rpcbind currently silently ignores any errors that occur during > > init_transport, it also happily continues if bind(2) fails for > > UDP socket - it's enough if just one UDP socket is bound. > > > > This patch makes rpcbind fail if there are problems with > > setting up any transport, so we don't end up with > > semi/non functional running daemon. > > Can you give us some details about why transport initialization was > failing? There are probably some cases where we do want rpcbind to > soldier on in spite of such troubles. An obvious example is when address given to '-h' option isn't there, or daemon can't bind to it for some reason. Bind fails, but rpcbind is running as if nothing happened. And, besides, behavior for UDP and TCP sockets is curently inconsistent as init_transport ignores any failed UDP bind and correctly returns error for TCP. The only legitimate reason for ignoring errors I may see here is when IPv6 is configured in /etc/netconfig but it's not set up on net interfaces, but as such case is administrative mistake it should be fixed by the admin, not the daemon. -- Jan Rękorajski | ALL SUSPECTS ARE GUILTY. PERIOD! baggins<at>mimuw.edu.pl | OTHERWISE THEY WOULDN'T BE SUSPECTS, WOULD THEY? BOFH, MANIAC | -- TROOPS by Kevin Rubio -- 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
