Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
liblongpath-rsync
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
liblongpath
liblongpath-rsync
Commits
c7d692c3
Commit
c7d692c3
authored
Apr 24, 2002
by
Martin Pool
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Notes about handling machines lacking getaddrinfo().
parent
f9b9e2f0
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
0 deletions
+9
-0
TODO
TODO
+9
-0
No files found.
TODO
View file @
c7d692c3
...
@@ -308,6 +308,15 @@ Hard-link handling
...
@@ -308,6 +308,15 @@ Hard-link handling
IPv6
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.
Implement suggestions from http://www.kame.net/newsletter/19980604/
Implement suggestions from http://www.kame.net/newsletter/19980604/
and ftp://ftp.iij.ad.jp/pub/RFC/rfc2553.txt
and ftp://ftp.iij.ad.jp/pub/RFC/rfc2553.txt
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment