"rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files
Go azure-blobazure-blob-storageazure-filesbackblaze-b2cloud-storagedropboxencryptionftpfuse-filesystemgogolanggoogle-cloud-storagegoogle-driveonedriveopenstack-swiftrclones3sftpsyncwebdav
docs: fix broken links and wrong s3 directory bucket flag name
shaurya9dbfd9d85231
diff --git a/docs/content/bisync.md b/docs/content/bisync.mdindex a7dff19ee..6198378cd 100644--- a/docs/content/bisync.md+++ b/docs/content/bisync.md@@ -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,essentially marking the file as needing to be rechecked next time.- 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,using the same "march" infrastructure as `check` and `sync`,for performance improvements and less@@ -1991,7 +1991,7 @@ behavior with new [`--conflict-resolve`](#conflict-resolve),[`--conflict-suffix`](#conflict-suffix) flags.- A new [`--resync-mode`](#resync-mode) flag allows more control over whichversion 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.)### `v1.64`diff --git a/docs/content/docs.md b/docs/content/docs.mdindex 14d563c32..ec57c4899 100644--- a/docs/content/docs.md+++ b/docs/content/docs.md@@ -1043,7 +1043,8 @@ will use this much memory for buffering.When using `mount` or `cmount` each open file descriptor will use this muchmemory 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.diff --git a/docs/content/s3.md b/docs/content/s3.mdindex 32d970ff4..98962229d 100644--- a/docs/content/s3.md+++ b/docs/content/s3.md@@ -4839,15 +4839,15 @@ section above.From rclone v1.69 [Directory Buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html)are supported.-You will need to set the `directory_buckets = true` config parameter-or use `--s3-directory-buckets`.+You will need to set the `directory_bucket = true` config parameter+or use `--s3-directory-bucket`.Note that rclone cannot yet:- Create 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 Edgediff --git a/docs/content/sftp.md b/docs/content/sftp.mdindex 8dd730f62..f15188483 100644--- a/docs/content/sftp.md+++ b/docs/content/sftp.md@@ -442,7 +442,7 @@ correct, and support all features.The shell type auto-detection logic, described above, means thatby default rclone will try to run a shell command the first timea 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 itwill re-run the command on every access. To avoid this you shouldexplicitly set the `shell_type` option to the correct value,