docs: fix markdownlint issue md009/no-trailing-spaces
This commit is contained in:
@@ -440,7 +440,7 @@ description: "Rclone Changelog"
|
||||
* Changed backends
|
||||
* [S3](/s3/) backend updated to use [AWS SDKv2](https://github.com/aws/aws-sdk-go-v2) as v1 is now unsupported.
|
||||
* The matrix of providers and auth methods is huge and there could be problems with obscure combinations.
|
||||
* Please report problems in a [new issue](https://github.com/rclone/rclone/issues/new/choose) on Github.
|
||||
* Please report problems in a [new issue](https://github.com/rclone/rclone/issues/new/choose) on Github.
|
||||
* New commands
|
||||
* [config encryption](/commands/rclone_config_encryption/): set, remove and check to manage config file encryption (Nick Craig-Wood)
|
||||
* New Features
|
||||
|
||||
+23
-23
@@ -282,9 +282,9 @@ However using the connection string syntax, this does work.
|
||||
|
||||
rclone copy "gdrive,shared_with_me:shared-file.txt" gdrive:
|
||||
|
||||
Note that the connection string only affects the options of the immediate
|
||||
backend. If for example gdriveCrypt is a crypt based on gdrive, then the
|
||||
following command **will not work** as intended, because
|
||||
Note that the connection string only affects the options of the immediate
|
||||
backend. If for example gdriveCrypt is a crypt based on gdrive, then the
|
||||
following command **will not work** as intended, because
|
||||
`shared_with_me` is ignored by the crypt backend:
|
||||
|
||||
rclone copy "gdriveCrypt,shared_with_me:shared-file.txt" gdriveCrypt:
|
||||
@@ -617,8 +617,8 @@ name of the log level to set with option `--log-level`, are case
|
||||
insensitive, e.g. `--log-level ERROR` and `--log-level error` are
|
||||
identical.
|
||||
|
||||
Options documented to take a `stringArray` parameter accept multiple
|
||||
values. To pass more than one value, repeat the option; for example:
|
||||
Options documented to take a `stringArray` parameter accept multiple
|
||||
values. To pass more than one value, repeat the option; for example:
|
||||
`--include value1 --include value2`. Other options may only accept a
|
||||
single value, and should only be specified once, but where the
|
||||
specified parameter may indicate a list of values separated by space
|
||||
@@ -893,21 +893,21 @@ objects to transfer is held in memory before the transfers start.
|
||||
|
||||
### --checkers int
|
||||
|
||||
Originally controlling just the number of file checkers to run in parallel,
|
||||
e.g. by `rclone copy`. Now a fairly universal parallelism control
|
||||
used by `rclone` in several places.
|
||||
Originally controlling just the number of file checkers to run in parallel,
|
||||
e.g. by `rclone copy`. Now a fairly universal parallelism control
|
||||
used by `rclone` in several places.
|
||||
|
||||
Note: checkers do the equality checking of files during a sync.
|
||||
For some storage systems (e.g. S3, Swift, Dropbox) this can take
|
||||
Note: checkers do the equality checking of files during a sync.
|
||||
For some storage systems (e.g. S3, Swift, Dropbox) this can take
|
||||
a significant amount of time so they are run in parallel.
|
||||
|
||||
The default is to run 8 checkers in parallel. However, in case
|
||||
The default is to run 8 checkers in parallel. However, in case
|
||||
of slow-reacting backends you may need to lower (rather than increase)
|
||||
this default by setting `--checkers` to 4 or less threads. This is
|
||||
especially advised if you are experiencing backend server crashes
|
||||
during file checking phase (e.g. on subsequent or top-up backups
|
||||
where little or no file copying is done and checking takes up
|
||||
most of the time). Increase this setting only with utmost care,
|
||||
this default by setting `--checkers` to 4 or less threads. This is
|
||||
especially advised if you are experiencing backend server crashes
|
||||
during file checking phase (e.g. on subsequent or top-up backups
|
||||
where little or no file copying is done and checking takes up
|
||||
most of the time). Increase this setting only with utmost care,
|
||||
while monitoring your server health and file checking throughput.
|
||||
|
||||
### -c, --checksum
|
||||
@@ -1089,7 +1089,7 @@ See `--compare-dest` and `--backup-dir`.
|
||||
|
||||
### --dedupe-mode interactive|skip|first|newest|oldest|largest|smallest|rename|list
|
||||
|
||||
Mode to run dedupe command in. One of `interactive`, `skip`, `first`,
|
||||
Mode to run dedupe command in. One of `interactive`, `skip`, `first`,
|
||||
`newest`, `oldest`, `largest`, `smallest`, `rename` `list`. The default
|
||||
is `interactive`. See the [dedupe](/commands/rclone_dedupe/) command
|
||||
for more information as to what these options mean.
|
||||
@@ -1393,7 +1393,7 @@ flag set) such as:
|
||||
|
||||
Without `--inplace` (the default) rclone will first upload to a
|
||||
temporary file with an extension like this, where `XXXXXX` represents a
|
||||
hash of the source file's fingerprint and `.partial` is
|
||||
hash of the source file's fingerprint and `.partial` is
|
||||
[--partial-suffix](#partial-suffix) value (`.partial` by default).
|
||||
|
||||
original-file-name.XXXXXX.partial
|
||||
@@ -3111,8 +3111,8 @@ override the environment variable setting.
|
||||
Or to always use the trash in drive `--drive-use-trash`, set
|
||||
`RCLONE_DRIVE_USE_TRASH=true`.
|
||||
|
||||
Verbosity is slightly different, the environment variable
|
||||
equivalent of `--verbose` or `-v` is `RCLONE_VERBOSE=1`,
|
||||
Verbosity is slightly different, the environment variable
|
||||
equivalent of `--verbose` or `-v` is `RCLONE_VERBOSE=1`,
|
||||
or for `-vv`, `RCLONE_VERBOSE=2`.
|
||||
|
||||
The same parser is used for the options and the environment variables
|
||||
@@ -3179,9 +3179,9 @@ $ rclone lsd MYS3:
|
||||
```
|
||||
|
||||
|
||||
Note that you can only set the options of the immediate backend,
|
||||
so RCLONE_CONFIG_MYS3CRYPT_ACCESS_KEY_ID has no effect, if myS3Crypt is
|
||||
a crypt remote based on an S3 remote. However RCLONE_S3_ACCESS_KEY_ID will
|
||||
Note that you can only set the options of the immediate backend,
|
||||
so RCLONE_CONFIG_MYS3CRYPT_ACCESS_KEY_ID has no effect, if myS3Crypt is
|
||||
a crypt remote based on an S3 remote. However RCLONE_S3_ACCESS_KEY_ID will
|
||||
set the access key of all remotes using S3, including myS3Crypt.
|
||||
|
||||
Note also that now rclone has [connection strings](#connection-strings),
|
||||
|
||||
@@ -15,7 +15,7 @@ image](https://securebuild.com/images/rclone) through our partner
|
||||
|
||||
## Release {{% version %}} OS requirements {#osrequirements}
|
||||
|
||||
| OS | Minimum Version |
|
||||
| OS | Minimum Version |
|
||||
|:-------:|:-------:|
|
||||
| Linux | Kernel 3.2 |
|
||||
| macOS | 11 (Big Sur) |
|
||||
@@ -118,7 +118,7 @@ script) from a URL which doesn't change then you can use these links.
|
||||
Older downloads can be found [here](https://downloads.rclone.org/).
|
||||
|
||||
The latest `rclone` version working for:
|
||||
| OS | Maximum rclone version |
|
||||
| OS | Maximum rclone version |
|
||||
|:-------:|:-------:|
|
||||
| Windows 7 | v1.63.1 |
|
||||
| Windows Server 2008 | v1.63.1 |
|
||||
|
||||
+1
-1
@@ -247,7 +247,7 @@ value, say `export GOGC=20`. This will make the garbage collector
|
||||
work harder, reducing memory size at the expense of CPU usage.
|
||||
|
||||
The most common cause of rclone using lots of memory is a single
|
||||
directory with millions of files in.
|
||||
directory with millions of files in.
|
||||
|
||||
Before rclone v1.70 has to load this entirely into memory as rclone
|
||||
objects. Each rclone object takes 0.5k-1k of memory. There is
|
||||
|
||||
+1
-1
@@ -19,7 +19,7 @@ If you just want to run a remote control then see the [rcd](/commands/rclone_rcd
|
||||
### --rc
|
||||
|
||||
Flag to start the http server listen on remote requests.
|
||||
|
||||
|
||||
### --rc-addr=IP
|
||||
|
||||
IPaddress:Port or :Port to bind server to. (default "localhost:5572").
|
||||
|
||||
Reference in New Issue
Block a user