- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for unlink (0.26 sec)
-
docs/bucket/notifications/README.md
MINIO_NOTIFY_AMQP_COMMENT (sentence) optionally add a comment to this setting ```
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 84K bytes - Viewed (2) -
docs/bucket/replication/README.md
## Highlights - Supports source and destination buckets to have the same name unlike AWS S3, addresses variety of usecases such as *Splunk*, *Veeam* site to site DR. - Supports object locking/retention across source and destination buckets natively out of the box, unlike AWS S3.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Jan 24 23:46:33 GMT 2023 - 18.2K bytes - Viewed (0) -
docs/debugging/README.md
### Remotely Inspecting backend data
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Feb 25 01:17:53 GMT 2022 - 8.7K bytes - Viewed (0) -
docs/distributed/README.md
A stand-alone MinIO server would go down if the server hosting the drives goes offline. In contrast, a distributed MinIO setup with _m_ servers and _n_ drives will have your data safe as long as _m/2_ servers or _m*n_/2 or more drives are online. For example, an 16-server distributed setup with 200 drives per node would continue serving files, up to 4 servers can be offline in default configuration i.e around 800 drives down MinIO would continue to read and write objects.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 8.8K bytes - Viewed (0)