Search Options

Results per page
Sort
Preferred Languages
Advance

Results 621 - 630 of 773 for wantSz (0.07 sec)

  1. cmd/testdata/xl-meta-merge.zip

    oding.html) for more complete documentation. ### Homebrew (recommended) Run the following command to install the latest stable MinIO package using [Homebrew](https://brew.sh/). Replace ``/data`` with the path to the drive or directory in which you want MinIO to store data. ```sh brew install minio/stable/minio minio server /data ``` > NOTE: If you previously installed minio using `brew install minio` then it is recommended that you reinstall minio from `minio/stable/minio` official repo instead....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Fri Mar 08 17:50:48 UTC 2024
    - 30.2K bytes
    - Viewed (0)
  2. CHANGELOG/CHANGELOG-1.2.md

    issues with Docker 1.9.1 can be found below.
      * CPU hardcapping will be enabled by default for containers with CPU limit set,
    if supported by the kernel. You should either adjust your CPU limit, or set CPU
    request only, if you want to avoid hardcapping. If the kernel does not support
    CPU Quota, NodeStatus will contain a warning indicating that CPU Limits cannot
    be enforced.
    Registered: Fri Nov 01 09:05:11 UTC 2024
    - Last Modified: Fri Dec 04 06:36:19 UTC 2020
    - 41.4K bytes
    - Viewed (0)
  3. helm-releases/minio-3.1.9.tgz

    version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ----------...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Sun Oct 10 21:28:04 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  4. helm-releases/minio-3.3.0.tgz

    version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ----------...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Nov 25 17:33:26 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  5. helm-releases/minio-3.4.0.tgz

    version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ----------...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Sun Dec 19 22:32:49 UTC 2021
    - 14.8K bytes
    - Viewed (0)
  6. helm-releases/minio-3.4.1.tgz

    version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ----------...
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Mon Dec 20 21:11:50 UTC 2021
    - 15.2K bytes
    - Viewed (0)
  7. LICENSE

    price.  Our General Public Licenses are designed to make sure that you
    have the freedom to distribute copies of free software (and charge for
    them if you wish), that you receive source code or can get it if you
    want it, that you can change the software or use pieces of it in new
    free programs, and that you know you can do these things.
    
      Developers that use our General Public Licenses protect your rights
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Fri Apr 23 18:58:53 UTC 2021
    - 33.7K bytes
    - Viewed (0)
  8. impl/maven-cli/src/main/java/org/apache/maven/cling/invoker/mvn/DefaultMavenInvoker.java

            // configuration. We don't have an easy way to allow a pluggable builder to provide its own configuration
            // parameters but this is sufficient for now. Ultimately we want components like Builders to provide a way to
            // extend the command line to accept its own configuration parameters.
            //
            if (context.invokerRequest.options().threads().isPresent()) {
    Registered: Sun Nov 03 03:35:11 UTC 2024
    - Last Modified: Fri Oct 25 12:31:46 UTC 2024
    - 29.8K bytes
    - Viewed (0)
  9. licenses/github.com/hashicorp/errwrap/LICENSE

          under the terms of any subsequent version published by the license
          steward.
    
    10.3. Modified Versions
    
          If you create software not governed by this License, and you want to
          create a new license for such software, you may create and use a modified
          version of this License if you rename the license and remove any
          references to the name of the license steward (except to note that such
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Sat Oct 26 02:47:39 UTC 2019
    - 15.6K bytes
    - Viewed (0)
  10. android/guava/src/com/google/common/hash/HashCode.java

      /**
       * Returns a "Java hash code" for this {@code HashCode} instance; this is well-defined (so, for
       * example, you can safely put {@code HashCode} instances into a {@code HashSet}) but is otherwise
       * probably not what you want to use.
       */
      @Override
      public final int hashCode() {
        // If we have at least 4 bytes (32 bits), just take the first 4 bytes. Since this is
    Registered: Fri Nov 01 12:43:10 UTC 2024
    - Last Modified: Wed Oct 30 19:54:59 UTC 2024
    - 12.6K bytes
    - Viewed (0)
Back to top