- Sort Score
- Num 10 results
- Language All
Results 1 - 9 of 9 for killCh (0.05 seconds)
The search processing time has exceeded the limit. The displayed results may be partial.
-
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]);Created: Tue Mar 31 13:07:34 GMT 2026 - Last Modified: Wed Jan 14 14:29:07 GMT 2026 - 10.6K bytes - Click Count (0) -
docs/en/docs/deployment/concepts.md
* Any program, any code, **can only do things** when it is being **executed**. So, when there's a **process running**. * The process can be **terminated** (or "killed") by you, or by the operating system. At that point, it stops running/being executed, and it can **no longer do things**.
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 05 18:13:19 GMT 2026 - 18.5K bytes - Click Count (1) -
docs/zh-hant/docs/deployment/concepts.md
### 什麼是行程 { #what-is-a-process } 「行程(process)」通常以更特定的方式使用,只指作業系統中正在執行的東西(如上面最後一點): - 在作業系統上「執行中」的特定程式。 - 這不是指檔案或原始碼,而是特指正在被作業系統執行並管理的那個東西。 - 任何程式、任何程式碼,只有在「被執行」時才能做事。所以,當有「行程在執行」時才能運作。 - 行程可以被你或作業系統終止(kill)。此時它就停止執行,無法再做任何事。 - 你電腦上執行的每個應用程式、每個視窗等,背後都有一些行程。而且在電腦開機時,通常會同時有許多行程在跑。 - 同一個程式可以同時有多個行程在執行。 如果你打開作業系統的「工作管理員」或「系統監控器」(或類似工具),就能看到許多正在執行的行程。 例如,你大概會看到同一個瀏覽器(Firefox、Chrome、Edge 等)會有多個行程在執行。它們通常每個分頁一個行程,外加其他一些額外行程。Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Fri Mar 20 17:05:38 GMT 2026 - 16.1K bytes - Click Count (0) -
docs/ko/docs/deployment/concepts.md
* 운영체제에서 **실행 중**인 특정 프로그램 * 파일이나 코드를 의미하는 것이 아니라, 운영체제가 **실제로 실행**하고 관리하는 대상을 **구체적으로** 의미합니다. * 어떤 프로그램이든 어떤 코드든, **실행**될 때만 무언가를 **할 수 있습니다**. 즉, **프로세스가 실행 중**일 때입니다. * 프로세스는 여러분이, 혹은 운영체제가 **종료**(또는 “kill”)할 수 있습니다. 그러면 실행이 멈추고, 더 이상 **아무것도 할 수 없습니다**. * 컴퓨터에서 실행 중인 각 애플리케이션 뒤에는 프로세스가 있습니다. 실행 중인 프로그램, 각 창 등도 마찬가지입니다. 그리고 컴퓨터가 켜져 있는 동안 보통 많은 프로세스가 **동시에** 실행됩니다. * **같은 프로그램**의 **여러 프로세스**가 동시에 실행될 수도 있습니다.Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Fri Mar 20 14:06:26 GMT 2026 - 21.2K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.32.md
- Added `singleProcessOOMKill` flag to the kubelet configuration. Setting that to true enable single process OOM killing in cgroups v2. In this mode, if a single process is OOM killed within a container, the remaining processes will not be OOM killed. ([#126096](https://github.com/kubernetes/kubernetes/pull/126096), [@utam0k](https://github.com/utam0k)) [SIG API Machinery, Node, Testing and Windows]
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Thu Feb 26 23:58:21 GMT 2026 - 470.5K bytes - Click Count (0) -
docs/ja/docs/deployment/concepts.md
* OS上で**実行**している特定のプログラム * これはファイルやコードを指すのではなく、OSによって**実行**され、管理されているものを指します。 * どんなプログラムやコードも、それが**実行されているときにだけ機能**します。つまり、**プロセスとして実行されているときだけ**です。 * プロセスは、ユーザーにあるいはOSによって、 **終了**(あるいは "kill")させることができます。その時点で、プロセスは実行/実行されることを停止し、それ以降は**何もできなくなります**。 * コンピュータで実行されている各アプリケーションは、実行中のプログラムや各ウィンドウなど、その背後にいくつかのプロセスを持っています。そして通常、コンピュータが起動している間、**多くのプロセスが**同時に実行されています。 * **同じプログラム**の**複数のプロセス**が同時に実行されていることがあります。Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Fri Mar 20 14:07:17 GMT 2026 - 24.5K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.35.md
- Slow container runtime initialization no longer causes the System WatchDog to kill the kubelet. The Device Manager was treated as unhealthy until it began listening on its port. ([#135153](https://github.com/kubernetes/kubernetes/pull/135153), [@SergeyKanzhelev](https://github.com/SergeyKanzhelev))
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Thu Mar 19 03:20:49 GMT 2026 - 265.9K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.34.md
- The slow initialization of container runtime will not cause System WatchDog to kill kubelet. Device Manager is not considered healthy before it attempted to start listening on the port. ([#135207](https://github.com/kubernetes/kubernetes/pull/135207), [@SergeyKanzhelev](https://github.com/SergeyKanzhelev)) [SIG Node]
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Thu Mar 19 03:19:43 GMT 2026 - 368.7K bytes - Click Count (2) -
CHANGELOG/CHANGELOG-1.33.md
- The slow initialization of container runtime will not cause System WatchDog to kill kubelet. Device Manager is not considered healthy before it attempted to start listening on the port. ([#135208](https://github.com/kubernetes/kubernetes/pull/135208), [@SergeyKanzhelev](https://github.com/SergeyKanzhelev)) [SIG Node]
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Thu Mar 19 03:17:58 GMT 2026 - 369K bytes - Click Count (0)