From b25d9810c5fdb3dfd52b9cd31d7497565e582be5 Mon Sep 17 00:00:00 2001 From: Stephane Gourichon Date: Thu, 30 Aug 2018 13:03:52 +0200 Subject: [PATCH] Fix bug 5792 by documenting existing behavior. This fulfills a wish by bug assignee Matt McCutchen https://bugzilla.samba.org/show_bug.cgi?id=5792 --- rsync.yo | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/rsync.yo b/rsync.yo index 71008576..59a31e92 100644 --- a/rsync.yo +++ b/rsync.yo @@ -1316,7 +1316,10 @@ unchanged, but may differ in some areas. Notably, a dry run does not send the actual data for file transfers, so bf(--progress) has no effect, the "bytes sent", "bytes received", "literal data", and "matched data" statistics are too small, and the "speedup" value is equivalent to a run -where no file transfers were needed. +where no file transfers were needed. Also, the log file (see +bf(--log-file=FILE)) will em(not) log all files that would have been +transferred, use (bf(-i, --itemize-changes)) or bf(--out-format='%i %n%L') +for that. dit(bf(-W, --whole-file)) This option disables rsync's delta-transfer algorithm, which causes all transferred files to be sent whole. The transfer may be @@ -2244,7 +2247,9 @@ to a file. This is similar to the logging that a daemon does, but can be requested for the client side and/or the server side of a non-daemon transfer. If specified as a client option, transfer logging will be enabled with a default format of "%i %n%L". See the bf(--log-file-format) -option if you wish to override this. +option if you wish to override this. em(Warning): in case of dry-run, this +does not provide the full list of what would have been transferred, only +(bf(-i, --itemize-changes)) or bf(--out-format='%i %n%L') provide that. Here's a example command that requests the remote side to log what is happening: -- 2.17.1