docs: fix broken links and wrong s3 directory bucket flag name

Several documentation links pointed at anchors or paths that no longer
resolve, and the S3 directory buckets section named the config option
and flag in the plural, which does not match the backend.

Co-authored-by: shaurya <19599684+no-hup@users.noreply.github.com>
Co-authored-by: no-hup <shauryaj.finance@gmail.com>
This commit is contained in:
shaurya
2026-08-26 17:42:57 +01:00
committed by GitHub
co-authored by shaurya no-hup
parent 660144d311
commit 9dbfd9d852
4 changed files with 8 additions and 7 deletions
+2 -2
View File
@@ -1961,7 +1961,7 @@ and far less prone to critical errors / undetected changes
- Bisync is now capable of rolling a file listing back in cases of uncertainty, - Bisync is now capable of rolling a file listing back in cases of uncertainty,
essentially marking the file as needing to be rechecked next time. essentially marking the file as needing to be rechecked next time.
- A few basic terminal colors are now supported, controllable with - A few basic terminal colors are now supported, controllable with
[`--color`](/docs/#color) (`AUTO`|`NEVER`|`ALWAYS`) [`--color`](/docs/#color-autoneveralways) (`AUTO`|`NEVER`|`ALWAYS`)
- Initial listing snapshots of Path1 and Path2 are now generated concurrently, - Initial listing snapshots of Path1 and Path2 are now generated concurrently,
using the same "march" infrastructure as `check` and `sync`, using the same "march" infrastructure as `check` and `sync`,
for performance improvements and less for performance improvements and less
@@ -1991,7 +1991,7 @@ behavior with new [`--conflict-resolve`](#conflict-resolve),
[`--conflict-suffix`](#conflict-suffix) flags. [`--conflict-suffix`](#conflict-suffix) flags.
- A new [`--resync-mode`](#resync-mode) flag allows more control over which - A new [`--resync-mode`](#resync-mode) flag allows more control over which
version of a file gets kept during a `--resync`. version of a file gets kept during a `--resync`.
- Bisync now supports [`--retries`](/docs/#retries-int) and [`--retries-sleep`](/docs/#retries-sleep-time) - Bisync now supports [`--retries`](/docs/#retries-int) and [`--retries-sleep`](/docs/#retries-sleep-duration)
(when [`--resilient`](#resilient) is set.) (when [`--resilient`](#resilient) is set.)
### `v1.64` ### `v1.64`
+2 -1
View File
@@ -1043,7 +1043,8 @@ will use this much memory for buffering.
When using `mount` or `cmount` each open file descriptor will use this much When using `mount` or `cmount` each open file descriptor will use this much
memory for buffering. memory for buffering.
See the [mount](/commands/rclone_mount/#file-buffering) documentation for more details. See the [mount](/commands/rclone_mount/#vfs-file-buffering) documentation for
more details.
Set to `0` to disable the buffering for the minimum memory usage. Set to `0` to disable the buffering for the minimum memory usage.
+3 -3
View File
@@ -4839,15 +4839,15 @@ section above.
From rclone v1.69 [Directory Buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html) From rclone v1.69 [Directory Buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html)
are supported. are supported.
You will need to set the `directory_buckets = true` config parameter You will need to set the `directory_bucket = true` config parameter
or use `--s3-directory-buckets`. or use `--s3-directory-bucket`.
Note that rclone cannot yet: Note that rclone cannot yet:
- Create directory buckets - Create directory buckets
- List directory buckets - List directory buckets
See [the --s3-directory-buckets flag](#s3-directory-buckets) for more info See [the --s3-directory-bucket flag](#s3-directory-bucket) for more info
### AWS Snowball Edge ### AWS Snowball Edge
+1 -1
View File
@@ -442,7 +442,7 @@ correct, and support all features.
The shell type auto-detection logic, described above, means that The shell type auto-detection logic, described above, means that
by default rclone will try to run a shell command the first time by default rclone will try to run a shell command the first time
a new sftp remote is accessed. If you configure a sftp remote a new sftp remote is accessed. If you configure a sftp remote
without a config file, e.g. an [on the fly](/docs/#backend-path-to-dir]) without a config file, e.g. an [on the fly](/docs/#backend-path-to-dir)
remote, rclone will have nowhere to store the result, and it remote, rclone will have nowhere to store the result, and it
will re-run the command on every access. To avoid this you should will re-run the command on every access. To avoid this you should
explicitly set the `shell_type` option to the correct value, explicitly set the `shell_type` option to the correct value,