- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 815 for Kill (0.03 sec)
-
src/test/java/org/codelibs/fess/util/JvmUtilTest.java
String[] args = new String[] { "11:-XX:OnOutOfMemoryError=\"kill -9 %p\"", "11:-Djava.awt.headless=true", "8-:-Dfile.encoding=UTF-8", "17-:-XX:+UseStringDeduplication" }; String[] result = JvmUtil.filterJvmOptions(args); assertEquals(3, result.length); assertEquals("-XX:OnOutOfMemoryError=\"kill -9 %p\"", result[0]); assertEquals("-Djava.awt.headless=true", result[1]);
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Sat Jul 12 07:34:10 UTC 2025 - 10.4K bytes - Viewed (0) -
src/main/java/org/codelibs/fess/auth/chain/CommandChain.java
process.destroy(); teminated = true; } catch (final Exception e) { if (logger.isInfoEnabled()) { logger.info("Could not kill the subprocess.", e); } } } } /** * Sets the finished flag to indicate whether the process has completed.
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Thu Jul 17 08:28:31 UTC 2025 - 13.1K bytes - Viewed (0) -
misc/go_android_exec/main.go
cmd := adbCmd("exec-out", args) cmd.Stdout = filter // If the adb subprocess somehow hangs, go test will kill this wrapper // and wait for our os.Stderr (and os.Stdout) to close as a result. // However, if the os.Stderr (or os.Stdout) file descriptors are // passed on, the hanging adb subprocess will hold them open and // go test will hang forever. // // Avoid that by wrapping stderr, breaking the short circuit and
Registered: Tue Sep 09 11:13:09 UTC 2025 - Last Modified: Mon Aug 21 17:46:57 UTC 2023 - 15.3K bytes - Viewed (0) -
docs/site-replication/run-multi-site-ldap.sh
sleep 10 val=$(./mc tag list minio1/newbucket --json | jq -r .tagset | jq -r .key) if [ "${val}" != "val1" ]; then echo "expected bucket tag to have replicated, exiting..." exit_1 fi # stop minio1 kill -9 ${site1_pid} # Update tag on minio2/newbucket when minio1 is down ./mc tag set minio2/newbucket "key=val2" # create a new bucket on minio2. This should replicate to minio1 after it comes online. ./mc mb minio2/newbucket2
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Sep 24 08:03:58 UTC 2024 - 10.1K bytes - Viewed (0) -
docs/site-replication/run-multi-site-minio-idp.sh
policy=$(./mc admin user info minio1 foobarx --json | jq -r .policyName) if [ "${policy}" != "null" ]; then echo "expected policy detach to have replicated, exiting..." exit_1 fi kill -9 ${site1_pid1} ${site1_pid2} # Update tag on minio2/newbucket when minio1 is down ./mc tag set minio2/newbucket "key=val2" # create a new bucket on minio2. This should replicate to minio1 after it comes online.
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Sep 24 08:03:58 UTC 2024 - 12.1K bytes - Viewed (0) -
helm-releases/minio-2.0.1.tgz
also turn on NetworkPolicy by setting the DefaultDeny namespace annotation. Note: this will enforce policy for _all_ pods in the namespace: ``` kubectl annotate namespace default "net.beta.kubernetes.io/network-policy={\"ingress\":{\"isolation\":\"DefaultDeny\"}}" ``` With NetworkPolicy enabled, traffic will be limited to just port 9000. For more precise policy, set `networkPolicy.allowExternal=true`. This will only allow pods with the generated client label to connect to MinIO. This label will be...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Aug 31 09:09:09 UTC 2021 - 13.6K bytes - Viewed (0) -
helm-releases/minio-3.0.0.tgz
also turn on NetworkPolicy by setting the DefaultDeny namespace annotation. Note: this will enforce policy for _all_ pods in the namespace: ``` kubectl annotate namespace default "net.beta.kubernetes.io/network-policy={\"ingress\":{\"isolation\":\"DefaultDeny\"}}" ``` With NetworkPolicy enabled, traffic will be limited to just port 9000. For more precise policy, set `networkPolicy.allowExternal=true`. This will only allow pods with the generated client label to connect to MinIO. This label will be...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Thu Sep 02 01:47:43 UTC 2021 - 13.8K bytes - Viewed (0) -
helm-releases/minio-1.0.2.tgz
must also turn on NetworkPolicy by setting the DefaultDeny namespace annotation. Note: this will enforce policy for _all_ pods in the namespace: kubectl annotate namespace default "net.beta.kubernetes.io/network-policy={\"ingress\":{\"isolation\":\"DefaultDeny\"}}" With NetworkPolicy enabled, traffic will be limited to just port 9000. For more precise policy, set `networkPolicy.allowExternal=true`. This will only allow pods with the generated client label to connect to MinIO. This label will be displayed...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Aug 24 18:58:05 UTC 2021 - 13.6K bytes - Viewed (0) -
helm-releases/minio-3.1.0.tgz
maxUnavailable: 1 ## Specify the service account to use for the Minio pods. If 'create' is set to 'false' ## and 'name' is left unspecified, the account 'default' will be used. serviceAccount: create: true ## The name of the service account to use. If 'create' is 'true', a service account with that name ## will be created. Otherwise, a name will be auto-generated. name: metrics: serviceMonitor: enabled: false additionalLabels: {} # namespace: monitoring # interval: 30s # scrapeTimeout: 10s minio/templates/NOTES.txt...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Sun Sep 12 18:19:27 UTC 2021 - 14.3K bytes - Viewed (0) -
helm-releases/minio-3.0.1.tgz
also turn on NetworkPolicy by setting the DefaultDeny namespace annotation. Note: this will enforce policy for _all_ pods in the namespace: ``` kubectl annotate namespace default "net.beta.kubernetes.io/network-policy={\"ingress\":{\"isolation\":\"DefaultDeny\"}}" ``` With NetworkPolicy enabled, traffic will be limited to just port 9000. For more precise policy, set `networkPolicy.allowExternal=true`. This will only allow pods with the generated client label to connect to MinIO. This label will be...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Thu Sep 02 01:47:43 UTC 2021 - 13.8K bytes - Viewed (0)