Tweak strace suggestion; get rid of really old issue.

[rsync-web.git] / issues.html

diff --git a/issues.html b/issues.html
index 26858d921c369341d1b251bad4db6b6e5a961fc6..7d5457d1362e23aa5e20addf5dfb22cc29a976de 100644 (file)
--- a/issues.html
+++ b/issues.html
@@ -67,7 +67,9 @@ figure out is <b>why</b>, and that can involve some investigative work.
 
 <p>If the remote rsync is a daemon, your first step should be to look at
 the daemon's log file to see if it logged an error explaining why it
-aborted the transfer.
+aborted the transfer.  Also double-check to ensure that the log file is
+setup right, as a wrong "log file" setting in your rsyncd.conf file can
+also cause this problem.
 
 <p>Beginning with version 2.6.3, rsync now does a better job of retreiving
 the error from the remote
@@ -82,7 +84,7 @@ see if you now get sent the error message from the remote rsync.
 size of the largest file that needs to be updated available in free
 disk space for the transfer to succeed).
 
-<li>An idle connection caused a router or remove-shell server to close
+<li>An idle connection caused a router or remote-shell server to close
 the connection.
 
 <li>A network error caused the connection to be dropped.
@@ -125,7 +127,7 @@ system-call tracing utility such as <i>strace</i>, <i>truss</i>, or
 tells strace to follow the child processes too):
 
 <pre>ulimit -c unlimited
-strace -f rsync --daemon --no-detach 2&gt;/tmp/rsync-$$.out
+strace -f -t -s 1024 -o /tmp/rsync-$$.out rsync --daemon --no-detach
 </pre>
 
 <p>Then, use a separate window to actually run the failing transfer, after
@@ -156,15 +158,6 @@ get returned to all rsync clients, old or new alike.
 
 <li><p><b>Q:</b>
 
-Why doesn't --dry-run (-n) show all the changed directories?
-
-<p><b>A:</b>
-
-This was a bug in versions prior to 2.6.4.  Upgrade both rsync versions (or at
-least the receiving side).
-
-<li><p><b>Q:</b>
-
 Aren't there more issues than this?
 
 <p><b>A:</b>