From: Martin Pool Date: Mon, 13 May 2002 07:54:47 +0000 (+0000) Subject: Note that using the old sockets API probably will not work X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/commitdiff_plain/bde47ca7c52ac6b3e9f5b9bb0823c7b2ceb42768 Note that using the old sockets API probably will not work sufficiently on some ipv6 systems. --- diff --git a/TODO b/TODO index 704e5793..79840312 100644 --- a/TODO +++ b/TODO @@ -313,14 +313,21 @@ Hard-link handling IPv6 - Put back the old socket code; if on a machine that does not properly - support the getaddrinfo API, then use it. This is probably much - simpler than reimplementing it. This might get us working again on - RedHat 5 and similar systems. Although the Kame patch seems like a - good idea, in fact it is a much broader interface than the - relatively narrow "open by name", "accept and log" interface that - rsync uses internally, and it has the disadvantage of clashing with - half-arsed implementations of the API. + Perhaps put back the old socket code; if on a machine that does not + properly support the getaddrinfo API, then use it. This is probably + much simpler than reimplementing it. + + Alternatively, have two different files implementing the same + interface, and choose either the new or the old API. This is + probably necessary for systems that e.g. have IPv6, but + gethostbyaddr() can't handle it. The Linux manpage claims this is + currently the case. + + This might get us working again on RedHat 5 and similar systems. + Although the Kame patch seems like a good idea, in fact it is a much + broader interface than the relatively narrow "open by name", "accept + and log" interface that rsync uses internally, and it has the + disadvantage of clashing with half-arsed implementations of the API. Implement suggestions from http://www.kame.net/newsletter/19980604/ and ftp://ftp.iij.ad.jp/pub/RFC/rfc2553.txt