Home • Explore • Blog • CI
☰



man-pages
70th chunk of `rsync.man`
1dd3ec815f8b1aea446bdad2558ea3119f8baaf5841134b20000000100000fcf
 than  1024
              bytes per second is possible.

              Rsync writes data over the socket in blocks, and this option both
              limits  the  size  of  the blocks that rsync writes, and tries to
              keep the average transfer rate  at  the  requested  limit.   Some
              burstiness may be seen where rsync writes out a block of data and
              then sleeps to bring the average rate into compliance.

              Due  to the internal buffering of data, the --progress option may
              not be an accurate reflection on how fast the data is being sent.
              This is because some files can show up as being rapidly sent when
              the data is quickly buffered, while other can  show  up  as  very
              slow  when the flushing of the output buffer occurs.  This may be
              fixed in a future version.

              See also the daemon version of the --bwlimit option.

       --stop‐after=MINS, (--time‐limit=MINS)
              This option tells rsync to stop copying when the specified number
              of minutes has elapsed.

              For maximal flexibility, rsync does not communicate  this  option
              to  the  remote rsync since it is usually enough that one side of
              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.

              The --time‐limit version of this option is deprecated.

       --stop‐at=y‐m‐dTh:m
              This  option tells rsync to stop copying when the specified point
              in time has been reached. The date & time can be fully  specified
              in   a   numeric   format   of  year‐month‐dayThour:minute  (e.g.
              2000‐12‐31T23:59) in the local timezone.  You may choose to sepa‐
              rate the date numbers using slashes instead of dashes.

              The value can also be abbreviated in a variety of ways,  such  as
              specifying  a 2‐digit year and/or leaving off various values.  In
              all cases, the value will be taken to be the next possible  point
              in  time  where  the  supplied information matches.  If the value
              specifies the current time or a past time, rsync  exits  with  an
              error.

              For  example, "1‐30" specifies the next January 30th (at midnight
              local time), "14:00" specifies the next 2 P.M., "1" specifies the
              next 1st of the month at midnight, "31" specifies the next  month
              where  we  can stop on its 31st day, and ":59" specifies the next
              59th minute after the hour.

              For maximal flexibility, rsync does not communicate  this  option
              to  the  remote rsync since it is usually enough that one side of
              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
Title: Rsync: Time Limits, File Synchronization, and Batch Writing
Summary
This section describes the `--stop-after=MINS` and `--stop-at=y-m-dTh:m` options, which limit the rsync transfer time. It also covers the `--fsync` option, which forces the receiving side to synchronize each finished file. Finally, it introduces the `--write-batch=FILE` option, used to record a file for later application to another identical destination, overriding checksum and compression negotiations.