Note about lchmod.

[rsync/rsync.git] / TODO

diff --git a/TODO b/TODO
index fe46584..c091d21 100644 (file)
--- a/TODO
+++ b/TODO
@@ -2,6 +2,13 @@
 
 BUGS ---------------------------------------------------------------
 
 
 BUGS ---------------------------------------------------------------
 

+rsync-url barfs on upload
+
+  rsync foo rsync://localhost/transfer/
+
+  Fix the parser.
+
+

 There seems to be a bug with hardlinks
 
   mbp/2 build$ ls -l /tmp/a /tmp/b -i
 There seems to be a bug with hardlinks
 
   mbp/2 build$ ls -l /tmp/a /tmp/b -i


@@ -92,9 +99,11 @@ Progress indicator can produce corrupt output when transferring directories:
   main/binary-arm/math/
   main/binary-arm/misc/
 
   main/binary-arm/math/
   main/binary-arm/misc/
 

+

 lchmod
   I don't think we handle this properly on systems that don't have the
 lchmod
   I don't think we handle this properly on systems that don't have the

-  call.
+  call.  Are there any such?
+

 
 Cross-test versions
   Part of the regression suite should be making sure that we don't
 
 Cross-test versions
   Part of the regression suite should be making sure that we don't


@@ -106,6 +115,15 @@ Cross-test versions
   some testing and also be the most common case for having different
   versions and not being able to upgrade.
 
   some testing and also be the most common case for having different
   versions and not being able to upgrade.
 

+--no-blocking-io might be broken
+
+  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 --------------------------------------------------------------
 
 
 DAEMON --------------------------------------------------------------
 


@@ -297,6 +315,22 @@ Hard-link handling
 
 IPv6
 
 
 IPv6
 

+  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
 
   Implement suggestions from http://www.kame.net/newsletter/19980604/
   and ftp://ftp.iij.ad.jp/pub/RFC/rfc2553.txt
 


@@ -476,6 +510,8 @@ chmod:
   the program.  For bonus points there would be a test case for the  
   parser.
 
   the program.  For bonus points there would be a test case for the  
   parser.
 

+  Possibly also --chown
+

   (Debian #23628)
 
 
   (Debian #23628)