mirror/rsync
1
0
Fork 0
mirror of https://github.com/RsyncProject/rsync.git synced 2026-05-18 20:06:07 -04:00
Code Issues Packages Projects Releases Wiki Activity

Note that using the old sockets API probably will not work

Browse Source 
sufficiently on some ipv6 systems.
This commit is contained in:
Martin Pool
2002-05-13 07:54:47 +00:00
parent ea7f8108b0
commit bde47ca7c5
1 changed files with 15 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
TODO
View File

@@ -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