On Mon, Apr 28, 2014 at 02:00:47PM +0200, Jeroen Massar wrote: > It is only a user-error from the perspective of disabling a current > protocol. If you disable IPv4 your host won't even boot, even if you > want it to be IPv6 only. > > Using IPv6 support of the networking API (getaddrinfo() and friends) is > a standard way of porting applications to support both IPv4 and IPv6.
mtr doesn't use "getaddrinfo". For a reason. Not a good reason, but for a reason. The reason is that it might have many address lookup requests active at the same time. And it needs to continue to send probe packets and process the replies. It cannot hang in the getaddrinfo call for five seconds. The IMHO correct way to handle this situation would have been to fork off a process that does the getaddrinfo call, and reports back to the main process. Alas, that wasn't the way things were implemented back in theold days, so now we're stuck in mtr with a separate name-resolving code-block which is buggy and difficult to maintain. Roger. -- +-- Rogier Wolff -- www.harddisk-recovery.nl -- 0800 220 20 20 -- - Datarecovery Services Nederland B.V. Delft. KVK: 30160549 - | Files foetsie, bestanden kwijt, alle data weg?! | Blijf kalm en neem contact op met Harddisk-recovery.nl! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org