X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/7c6ea3d8c7b8723c81803c8e81bd2d5c3daae563..d697314b42048356705cd7ad28e8e0030e2c309e:/rsync.yo diff --git a/rsync.yo b/rsync.yo index 4b20d9db..3515588b 100644 --- a/rsync.yo +++ b/rsync.yo @@ -341,6 +341,7 @@ to the detailed description below for a complete description. verb( --force force deletion of dirs even if not empty --max-delete=NUM don't delete more than NUM files --max-size=SIZE don't transfer any file larger than SIZE + --min-size=SIZE don't transfer any file smaller than SIZE --partial keep partially transferred files --partial-dir=DIR put a partially transferred file into DIR --delay-updates put all updated files into place at end @@ -799,9 +800,24 @@ This is useful when mirroring very large trees to prevent disasters. dit(bf(--max-size=SIZE)) This tells rsync to avoid transferring any file that is larger than the specified SIZE. The SIZE value can be -suffixed with a letter to indicate a size multiplier (K, M, or G) and +suffixed with a string to indicate a size multiplier, and may be a fractional value (e.g. "bf(--max-size=1.5m)"). +The suffixes are as follows: "K" (or "k") is a kilobyte (1024), +"M" (or "m") is a megabyte (1024*1024), and "G" (or "g") is a +gigabyte (1024*1024*1024). +If you want the multiplier to be 1000 instead of 1024, suffix the K, G, or +M with a "T" (or "t") to indicate that a power of 10 is desired. +Finally, if the suffix ends in either "+1" or "-1", the value will +be offset by one byte in the indicated direction. +Examples: --max-size=1.5mt-1 is 1499999 bytes, and --max-size=2g+1 is +2147483649 bytes. + +dit(bf(--min-size=SIZE)) This tells rsync to avoid transferring any +file that is smaller than the specified SIZE, which can help in not +transferring small, junk files. +See the bf(--max-size) option for a description of SIZE. + dit(bf(-B, --block-size=BLOCKSIZE)) This forces the block size used in the rsync algorithm to a fixed value. It is normally selected based on the size of each file being updated. See the technical report for details.