TrueCloudLab/rclone
16
0
Fork 2
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions 1

docs: fix and reword --update docs

Browse source 
After discussion on the forum with @bandwidth, this rewords the
--update docs to be correct and easier to understand.

See: https://forum.rclone.org/t/help-understanding-update/28937
This commit is contained in:
Nick Craig-Wood 2022-01-31 17:09:11 +00:00
parent 051685baa1
commit 0ae39bda8d
1 changed files with 20 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

34
docs/content/docs.md
View file

@ -1791,24 +1791,30 @@ The default is to run 4 file transfers in parallel.
This forces rclone to skip any files which exist on the destination This forces rclone to skip any files which exist on the destination
and have a modified time that is newer than the source file. and have a modified time that is newer than the source file.
This can be useful when transferring to a remote which doesn't support This can be useful in avoiding needless transfers when transferring to
mod times directly (or when using `--use-server-modtime` to avoid extra a remote which doesn't support modification times directly (or when
API calls) as it is more accurate than a `--size-only` check and faster using `--use-server-modtime` to avoid extra API calls) as it is more
than using `--checksum`. accurate than a `--size-only` check and faster than using
`--checksum`. On such remotes (or when using `--use-server-modtime`)
the time checked will be the uploaded time.
If an existing destination file has a modification time older than the
source file's, it will be updated if the sizes are different. If the
sizes are the same, it will be updated if the checksum is different or
not available.
If an existing destination file has a modification time equal (within If an existing destination file has a modification time equal (within
the computed modify window precision) to the source file's, it will be the computed modify window) to the source file's, it will be updated
updated if the sizes are different. If `--checksum` is set then if the sizes are different. The checksum will not be checked in this
rclone will update the destination if the checksums differ too. case unless the `--checksum` flag is provided.
If an existing destination file is older than the source file then In all other cases the file will not be updated.
it will be updated if the size or checksum differs from the source file.
On remotes which don't support mod time directly (or when using Consider using the `--modify-window` flag to compensate for time skews
`--use-server-modtime`) the time checked will be the uploaded time. between the source and the backend, for backends that do not support
This means that if uploading to one of these remotes, rclone will skip mod times, and instead use uploaded times. However, if the backend
any files which exist on the destination and have an uploaded time that does not support checksums, note that sync'ing or copying within the
is newer than the modification time of the source file. time skew window may still result in additional transfers for safety.
### --use-mmap ### ### --use-mmap ###