Timeline for Using cgroup to limit program memory as it's running
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 6, 2021 at 17:48 | history | edited | Ben | CC BY-SA 4.0 |
added 466 characters in body
|
| Jul 6, 2021 at 14:51 | history | edited | Ben | CC BY-SA 4.0 |
added 48 characters in body
|
| Jul 6, 2021 at 14:50 | comment | added | Ben | @Bouncner I mean, if it is not possible for the kernel to reduce the working set of the process below the new hard limit, then the kernel will not set the new hard limit, and the old value will be retained. In this case you can kill the process yourself or pick a higher limit. | |
| Jul 6, 2021 at 8:39 | comment | added | Bouncner |
What exactly do you mean by "If it is not possible to do this initially"? That sounds like I cannot set a group limit of 10 GB and then start a process with that group, but that's possible with "cgexec -g, isn't it? Can you clarify what you mean by that?
|
|
| Nov 25, 2020 at 23:08 | history | answered | Ben | CC BY-SA 4.0 |