Search Options

Results per page
Sort
Preferred Languages
Advance

Results 51 - 60 of 249 for attach (0.12 sec)

  1. LICENSES/vendor/github.com/coredns/caddy/LICENSE

          of your accepting any such warranty or additional liability.
    
       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "{}"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Sun Jun 13 05:06:37 UTC 2021
    - 11.2K bytes
    - Viewed (0)
  2. LICENSES/vendor/github.com/coredns/corefile-migration/LICENSE

          of your accepting any such warranty or additional liability.
    
       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.2K bytes
    - Viewed (0)
  3. LICENSES/vendor/github.com/coreos/go-oidc/LICENSE

          of your accepting any such warranty or additional liability.
    
       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "{}"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.2K bytes
    - Viewed (0)
  4. LICENSES/vendor/github.com/distribution/reference/LICENSE

          of your accepting any such warranty or additional liability.
    
       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "{}"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri Sep 01 01:53:40 UTC 2023
    - 11.2K bytes
    - Viewed (0)
  5. LICENSES/vendor/github.com/go-logr/logr/LICENSE

          of your accepting any such warranty or additional liability.
    
       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "{}"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Sat May 16 11:52:51 UTC 2020
    - 11.2K bytes
    - Viewed (0)
  6. LICENSE

          of your accepting any such warranty or additional liability.
    
       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
    Registered: Fri Sep 05 12:43:10 UTC 2025
    - Last Modified: Wed Feb 22 18:59:39 UTC 2023
    - 11.1K bytes
    - Viewed (0)
  7. docs/site-replication/run-multi-site-ldap.sh

    export MC_HOST_minio3=http://minio:minio123@localhost:9003
    
    ./mc ready minio1
    ./mc ready minio2
    ./mc ready minio3
    
    ./mc admin replicate add minio1 minio2 minio3
    
    ./mc idp ldap policy attach minio1 consoleAdmin --user="uid=dillon,ou=people,ou=swengg,dc=min,dc=io"
    sleep 5
    
    ./mc admin user info minio2 "uid=dillon,ou=people,ou=swengg,dc=min,dc=io"
    ./mc admin user info minio3 "uid=dillon,ou=people,ou=swengg,dc=min,dc=io"
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Sep 24 08:03:58 UTC 2024
    - 10.1K bytes
    - Viewed (0)
  8. LICENSE

    possible use to the public, the best way to achieve this is to make it
    free software which everyone can redistribute and change under these terms.
    
      To do so, attach the following notices to the program.  It is safest
    to attach them to the start of each source file to most effectively
    state the exclusion of warranty; and each file should have at least
    the "copyright" line and a pointer to where the full notice is found.
    
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Fri Apr 23 18:58:53 UTC 2021
    - 33.7K bytes
    - Viewed (0)
  9. CHANGELOG/CHANGELOG-1.18.md

    - Fixes issue where you can't attach more than 15 GCE Persistent Disks to c2, n2, m1, m2 machine types. ([#88602](https://github.com/kubernetes/kubernetes/pull/88602), [@yuga711](https://github.com/yuga711)) [SIG Storage]
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Wed Jun 16 17:18:28 UTC 2021
    - 373.2K bytes
    - Viewed (0)
  10. LICENSE

          of your accepting any such warranty or additional liability.
    
       END OF TERMS AND CONDITIONS
    
       APPENDIX: How to apply the Apache License to your work.
    
          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
    Registered: Thu Sep 04 12:52:25 UTC 2025
    - Last Modified: Tue May 08 21:35:34 UTC 2018
    - 11.1K bytes
    - Viewed (0)
Back to top