diff options
author | Wayne Davison <wayned@samba.org> | 2007-11-08 00:06:48 +0000 |
---|---|---|
committer | Wayne Davison <wayned@samba.org> | 2007-11-08 00:06:48 +0000 |
commit | d100e733db1c34030385e46dae47fdbf1984de60 (patch) | |
tree | ae0de1332664a581c50fd5e48f57dfc35172e7df /rsync.yo | |
parent | 15e4d4018491e01ea36b773aa6165a62481d6f31 (diff) | |
download | rsync-d100e733db1c34030385e46dae47fdbf1984de60.tar.gz rsync-d100e733db1c34030385e46dae47fdbf1984de60.tar.bz2 rsync-d100e733db1c34030385e46dae47fdbf1984de60.zip |
Improve the man page and --help descriptions of --dry-run. In
particular, make it clear that --dry-run turns off action without
turning on verbosity, and has some incomplete/inaccurate stats.
Diffstat (limited to 'rsync.yo')
-rw-r--r-- | rsync.yo | 18 |
1 files changed, 15 insertions, 3 deletions
@@ -352,7 +352,7 @@ to the detailed description below for a complete description. verb( --super receiver attempts super-user activities --fake-super store/recover privileged attrs using xattrs -S, --sparse handle sparse files efficiently - -n, --dry-run show what would have been transferred + -n, --dry-run perform a trial run with no changes made -W, --whole-file copy files whole (without rsync algorithm) -x, --one-file-system don't cross filesystem boundaries -B, --block-size=SIZE force a fixed checksum block-size @@ -1022,8 +1022,20 @@ NOTE: Don't use this option when the destination is a Solaris "tmpfs" filesystem. It doesn't seem to handle seeks over null regions correctly and ends up corrupting the files. -dit(bf(-n, --dry-run)) This tells rsync to not do any file transfers, -instead it will just report the actions it would have taken. +dit(bf(-n, --dry-run)) This makes rsync perform a trial run that doesn't +make any changes (and produces mostly the same output as a real run). It +is most commonly used in combination with the bf(-v, --verbose) and/or +bf(-i, --itemize-changes) options to see what an rsync command is going +to do before one actually runs it. + +The output of bf(--itemize-changes) is supposed to be exactly the same on a +dry run and a subsequent real run (barring intentional trickery and system +call failures); if it isn't, that's a bug. Other output is the same to the +extent practical, 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 are needed. dit(bf(-W, --whole-file)) With this option the delta transfer algorithm is not used and the whole file is sent as-is instead. The transfer may be |