diff options
| author | Wayne Davison <wayned@samba.org> | 2015-07-12 13:10:05 -0700 |
|---|---|---|
| committer | Wayne Davison <wayned@samba.org> | 2015-07-12 13:10:05 -0700 |
| commit | 0bcb8b639af6ede0f28de16a5ef3f00b4153dc2b (patch) | |
| tree | cd5c44c350ecc7613c55d4b3ff5055d3fc2d1660 | |
| parent | 77f750f1679a1aedbb95c2fa11323c4c16c26498 (diff) | |
| download | android_external_rsync-0bcb8b639af6ede0f28de16a5ef3f00b4153dc2b.tar.gz android_external_rsync-0bcb8b639af6ede0f28de16a5ef3f00b4153dc2b.tar.bz2 android_external_rsync-0bcb8b639af6ede0f28de16a5ef3f00b4153dc2b.zip | |
Mention local-only effect of --msgs2stderr.
| -rw-r--r-- | rsync.yo | 4 |
1 files changed, 3 insertions, 1 deletions
@@ -571,7 +571,9 @@ directly to stderr rather than to send messages to the client side via the protocol (which normally outputs info messages via stdout). This is mainly intended for debugging in order to avoid changing the data sent via the protocol, since the extra protocol data can change what is being tested. -Keep in mind that a daemon connection does not have a stderr channel to send +The option does not affect the remote side of a transfer without using +bf(--remote-option) -- e.g. bf(-M--msgs2stderr). +Also keep in mind that a daemon connection does not have a stderr channel to send messages back to the client side, so if you are doing any daemon-transfer debugging using this option, you should start up a daemon using bf(--no-detach) so that you can see the stderr output on the daemon side. |