Timeline for How to limit a systemd service to "play nice" with the CPU?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Oct 31, 2023 at 13:19 | history | edited | Caleb | CC BY-SA 4.0 | fixed typo on "cuplimit" -> "cpulimit" |
| S Oct 31, 2023 at 13:19 | history | suggested | CommunityBot | CC BY-SA 4.0 | fixed typo on "cuplimit" -> "cpulimit" |
| Oct 31, 2023 at 9:32 | review | Suggested edits | |||
| S Oct 31, 2023 at 13:19 | |||||
| Jul 17, 2022 at 16:02 | comment | added | ckujau | On my system (running systemd v250) that systemctl daemon-reload step was not needed but was done automatically, although people report that it's still needed. Anyway, thanks for that answer! | |
| Mar 21, 2022 at 10:43 | comment | added | Gen.Stack | Excellent. Thank you. Years ago I struggled to restrain clamav from hogging CPU and RAM while using the tools available at that time. Namely cgroups and consorts. That was before the rise of systemd, for which I am grateful. Since systemd so many things are configurable consistently and reliably. At least from my perspective.I just works (better and better). | |
| Mar 14, 2019 at 14:03 | vote | accept | Caleb | ||
| Jan 17, 2019 at 10:22 | history | answered | Caleb | CC BY-SA 4.0 |