mirror of
https://github.com/RsyncProject/rsync.git
synced 2026-05-19 12:25:42 -04:00
Improve description of --max-delete.
This commit is contained in:
10
rsync.yo
10
rsync.yo
@@ -1422,15 +1422,17 @@ using bf(--delete-after), and it used to be non-functional unless the
|
||||
bf(--recursive) option was also enabled.
|
||||
|
||||
dit(bf(--max-delete=NUM)) This tells rsync not to delete more than NUM
|
||||
files or directories. If that limit is exceeded, a warning is output
|
||||
and rsync exits with an error code of 25 (new for 3.0.0).
|
||||
files or directories. If that limit is exceeded, all further deletions are
|
||||
skipped through the end of the transfer. At the end, rsync outputs a warning
|
||||
(including a count of the skipped deletions) and exits with an error code
|
||||
of 25 (unless some more important error condition also occurred).
|
||||
|
||||
Also new for version 3.0.0, you may specify bf(--max-delete=0) to be warned
|
||||
Beginning with version 3.0.0, you may specify bf(--max-delete=0) to be warned
|
||||
about any extraneous files in the destination without removing any of them.
|
||||
Older clients interpreted this as "unlimited", so if you don't know what
|
||||
version the client is, you can use the less obvious bf(--max-delete=-1) as
|
||||
a backward-compatible way to specify that no deletions be allowed (though
|
||||
older versions didn't warn when the limit was exceeded).
|
||||
really old versions didn't warn when the limit was exceeded).
|
||||
|
||||
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
|
||||
|
||||
Reference in New Issue
Block a user