diff options
author | Wayne Davison <wayned@samba.org> | 2014-12-31 11:12:55 -0800 |
---|---|---|
committer | Wayne Davison <wayned@samba.org> | 2014-12-31 13:10:46 -0800 |
commit | ae189e18ded7a306a2d5516fbd5b7112c784e333 (patch) | |
tree | 2de241941e8e9528a4836697b960d7095e7bd6db | |
parent | 5b34561cf77962fe1286a5cb20f6bc25f7b6e345 (diff) | |
download | android_external_rsync-ae189e18ded7a306a2d5516fbd5b7112c784e333.tar.gz android_external_rsync-ae189e18ded7a306a2d5516fbd5b7112c784e333.tar.bz2 android_external_rsync-ae189e18ded7a306a2d5516fbd5b7112c784e333.zip |
Mention that --append can be dangerous.
-rw-r--r-- | rsync.yo | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -864,6 +864,11 @@ Implies bf(--inplace), but does not conflict with bf(--sparse) (since it is always extending a file's length). +The use of bf(--append) can be dangerous if you aren't 100% sure that the files +that are longer have only grown by the appending of data onto the end. You +should thus use include/exclude/filter rules to ensure that such a transfer is +only affecting files that you know to be growing via appended data. + dit(bf(--append-verify)) This works just like the bf(--append) option, but the existing data on the receiving side is included in the full-file checksum verification step, which will cause a file to be resent if the |