in the same way as --no-whole-file; somebody needs to check.
+Do not rely on having a group called "nobody"
+
+ http://www.linuxbase.org/spec/refspecs/LSB_1.1.0/gLSB/usernames.html
+
+ On Debian it's "nogroup"
DAEMON --------------------------------------------------------------
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
the program. For bonus points there would be a test case for the
parser.
+ Possibly also --chown
+
(Debian #23628)