This  option
              suppresses  that  error,  and  does not try to transfer the file.
              This does not affect subsequent vanished‐file errors  if  a  file
              was initially found to be present and later is no longer there.

       --delete‐missing‐args
              This option takes the behavior of the (implied) --ignore‐missing‐
              args  option a step farther: each missing arg will become a dele‐
              tion request of the corresponding destination file on the receiv‐
              ing side (should it exist).  If the destination file  is  a  non‐
              empty  directory, it will only be successfully deleted if --force
              or --delete are in effect.  Other than that, this option is inde‐
              pendent of any other type of delete processing.

              The missing source files are represented by special file‐list en‐
              tries which display as a "*missing" entry in the --list‐only out‐
              put.

       --ignore‐errors
              Tells --delete to go ahead and delete files even when  there  are
              I/O errors.

       --force
              This  option  tells rsync to delete a non‐empty directory when it
              is to be replaced by a non‐directory.  This is only  relevant  if
              deletions are not active (see --delete for details).

              Note  for older rsync versions: --force used to still be required
              when using --delete‐after, and it used to be  non‐functional  un‐
              less the --recursive option was also enabled.

       --max‐delete=NUM
              This  tells  rsync  not to delete more than NUM files or directo‐
              ries.  If that limit  is  exceeded,  all  further  deletions  are
              skipped  through the end of the transfer.  At the end, rsync out‐
              puts 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).

              Beginning with version 3.0.0, you may specify  --max‐delete=0  to
              be  warned  about any extraneous files in the destination without
              removing any of them.  Older clients interpreted this as  "unlim‐
              ited",  so  if you don’t know what version the client is, you can
              use the less obvious --max‐delete=-1 as a backward‐compatible way
              to specify that no deletions be allowed (though really  old  ver‐
              sions didn’t warn when the limit was exceeded).

       --max‐size=SIZE
              This  tells  rsync  to avoid transferring any file that is larger
              than the specified SIZE.  A numeric value can be suffixed with  a
              string to indicate the numeric units or left unqualified to spec‐
              ify  bytes.   Feel  free to use a fractional value along with the
              units, such as --max‐size=1.5m.

              This option is a TRANSFER RULE, so don’t expect any exclude  side
              effects.

              The  first letter of a units string can be B (bytes), K (kilo), M
              (mega), G (giga), T (tera), or P (peta).  If the string is a sin‐
              gle char or has "ib" added to it (e.g. "G"  or  "GiB")  then  the
              units are multiples of 1024.  If you use a two‐letter suffix that
              ends with a "B" (e.g. "kb") then you get units that are multiples
              of 1000.  The string’s letters can be any mix of upper and lower‐
              case that you want to use.

              Finally,  if the string ends with either "+1" or "-1", it is off‐
              set by one byte in the indicated direction.  The largest possible
              value is usually 8192P‐1.

              Examples:  --max‐size=1.5mb‐1  is  1499999  bytes,   and   --max‐
              size=2g+1 is 2147483649 bytes.

              Note  that  rsync  versions  prior  to