the connection quits as specified.  This allows the option’s  use
              even  when  only one side of the connection supports it.  You can
              tell the remote side about the time limit  using  --remote‐option
              (-M),  should  the  need  arise.  Do keep in mind that the remote
              host may have a different default timezone than your local host.

       --fsync
              Cause the receiving side to fsync each finished file.   This  may
              slow  down  the  transfer,  but can help to provide peace of mind
              when updating critical files.

       --write‐batch=FILE
              Record a file that can later be applied to another identical des‐
              tination with --read‐batch.  See the "BATCH MODE" section for de‐
              tails, and also the --only‐write‐batch option.

              This option overrides the negotiated checksum  &  compress  lists
              and  always  negotiates a choice based on old‐school md5/md4/zlib
              choices.  If you want a more modern choice, use  the  --checksum‐
              choice (--cc) and/or --compress‐choice (--zc) options.

       --only‐write‐batch=FILE
              Works  like --write‐batch, except that no updates are made on the
              destination system when creating the batch.  This lets you trans‐
              port the changes to the destination system via some  other  means
              and then apply the changes via --read‐batch.

              Note  that  you can feel free to write the batch directly to some
              portable media: if this media fills to capacity before the end of
              the transfer, you can just apply that  partial  transfer  to  the
              destination  and  repeat the whole process to get the rest of the
              changes (as long as you don’t mind a partially  updated  destina‐
              tion system while the multi‐update cycle is happening).

              Also  note that you only save bandwidth when pushing changes to a
              remote system because this allows the batched data to be diverted
              from the sender into the batch file without having to  flow  over
              the wire to the receiver (when pulling, the sender is remote, and
              thus can’t write the batch).

       --read‐batch=FILE
              Apply all of the changes stored in FILE, a file previously gener‐
              ated by --write‐batch.  If FILE is -, the batch data will be read
              from standard input. See the "BATCH MODE" section for details.

       --protocol=NUM
              Force  an  older protocol version to be used.  This is useful for
              creating a batch file that is compatible with an older version of
              rsync.  For instance, if rsync  2.6.4  is  being  used  with  the
              --write‐batch option, but rsync 2.6.3 is what will be used to run
              the --read‐batch option, you should use "--protocol=28" when cre‐
              ating  the  batch  file to force the older protocol version to be
              used in the batch file (assuming you can’t upgrade the  rsync  on
              the reading system).

       --iconv=CONVERT_SPEC
              Rsync can convert filenames between character sets using this op‐
              tion.  Using a CONVERT_SPEC of "." tells rsync to look up the de‐
              fault character‐set via the locale setting.  Alternately, you can
              fully  specify  what conversion to do by giving a local and a re‐
              mote charset separated by a comma in the order  --iconv=LOCAL,RE‐
              MOTE,  e.g.  --iconv=utf8,iso88591.   This order ensures that the
              option will stay the  same  whether  you’re  pushing  or  pulling
              files.   Finally,  you  can  specify  either --no‐iconv or a CON‐
              VERT_SPEC of "-" to turn off any conversion.  The default setting
              of this option is