github-mirror/rclone
2
0
Fork 0
mirror of https://github.com/rclone/rclone.git synced 2024-11-22 14:06:44 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: fix --use-server-modtime spelling in docs

Browse Source
This commit is contained in:
Bryce Larson 2019-10-14 19:14:10 -06:00 committed by Nick Craig-Wood
parent af05e290cf
commit dd150efdd7
4 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
MANUAL.html generated
View File

@ -2608,8 +2608,8 @@ rclone sync /path/to/files remote:current-backup</code></pre>
<h3 id="u-update">-u, –update</h3>
<p>This forces rclone to skip any files which exist on the destination and have a modified time that is newer than the source file.</p>
<p>If an existing destination file has a modification time equal (within the computed modify window precision) to the source file’s, it will be updated if the sizes are different.</p>
<p>On remotes which don’t support mod time directly (or when using <code>--use-server-mod-time</code>) the time checked will be the uploaded time. This means that if uploading to one of these remotes, rclone will skip any files which exist on the destination and have an uploaded time that is newer than the modification time of the source file.</p>
<p>This can be useful when transferring to a remote which doesn’t support mod times directly (or when using <code>--use-server-mod-time</code> to avoid extra API calls) as it is more accurate than a <code>--size-only</code> check and faster than using <code>--checksum</code>.</p>
<p>On remotes which don’t support mod time directly (or when using <code>--use-server-modtime</code>) the time checked will be the uploaded time. This means that if uploading to one of these remotes, rclone will skip any files which exist on the destination and have an uploaded time that is newer than the modification time of the source file.</p>
<p>This can be useful when transferring to a remote which doesn’t support mod times directly (or when using <code>--use-server-modtime</code> to avoid extra API calls) as it is more accurate than a <code>--size-only</code> check and faster than using <code>--checksum</code>.</p>
<h3 id="use-mmap">–use-mmap</h3>
<p>If this flag is set then rclone will use anonymous memory allocated by mmap on Unix based platforms and VirtualAlloc on Windows for its transfer buffers (size controlled by <code>--buffer-size</code>). Memory allocated like this does not go on the Go heap and can be returned to the OS immediately when it is finished with.</p>
<p>If this flag is not set then rclone will allocate and free the buffers using the Go memory allocator which may use more memory as memory pages are returned less aggressively to the OS.</p>

4
MANUAL.md generated
View File

@ -5629,13 +5629,13 @@ the computed modify window precision) to the source file's, it will be
updated if the sizes are different.
On remotes which don't support mod time directly (or when using
`--use-server-mod-time`) the time checked will be the uploaded time.
`--use-server-modtime`) the time checked will be the uploaded time.
This means that if uploading to one of these remotes, rclone will skip
any files which exist on the destination and have an uploaded time that
is newer than the modification time of the source file.
This can be useful when transferring to a remote which doesn't support
mod times directly (or when using `--use-server-mod-time` to avoid extra
mod times directly (or when using `--use-server-modtime` to avoid extra
API calls) as it is more accurate than a `--size-only` check and faster
than using `--checksum`.

4
MANUAL.txt generated
View File

@ -5267,13 +5267,13 @@ the computed modify window precision) to the source file’s, it will be
updated if the sizes are different.
On remotes which don’t support mod time directly (or when using
--use-server-mod-time) the time checked will be the uploaded time. This
--use-server-modtime) the time checked will be the uploaded time. This
means that if uploading to one of these remotes, rclone will skip any
files which exist on the destination and have an uploaded time that is
newer than the modification time of the source file.
This can be useful when transferring to a remote which doesn’t support
mod times directly (or when using --use-server-mod-time to avoid extra
mod times directly (or when using --use-server-modtime to avoid extra
API calls) as it is more accurate than a --size-only check and faster
than using --checksum.

4
docs/content/docs.md
View File

@ -1099,7 +1099,7 @@ This forces rclone to skip any files which exist on the destination
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
mod times directly (or when using `--use-server-mod-time` to avoid extra
mod times directly (or when using `--use-server-modtime` to avoid extra
API calls) as it is more accurate than a `--size-only` check and faster
than using `--checksum`.
@ -1112,7 +1112,7 @@ If an existing destination file is older than the source file then
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
`--use-server-mod-time`) the time checked will be the uploaded time.
`--use-server-modtime`) the time checked will be the uploaded time.
This means that if uploading to one of these remotes, rclone will skip
any files which exist on the destination and have an uploaded time that
is newer than the modification time of the source file.