mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #4354] cpulimit limits #2629
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#2629
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rusty-snake on GitHub (Jun 10, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4354
Currently we have
--cputo limit cores and--rlimit-cputo limit the total time.IMO this would be a good addition.
The project seems to be dead (last commit 17 Jun 2015) but it is packaged in the most distros as I see it.
IDC if you call
cpulimit(which need it installed), integrated it's code (GPLv2+ too) or implement your own code.@reinerh commented on GitHub (Jun 10, 2021):
This is also possible with cgroups:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/sect-cpu-example_usage
Which is a bit nicer than cpulimit, as the cgroup limits will be enforced by the kernel.
From a quick glance cpulimit is sending
SIGSTOP/SIGCONTto processes to enforce the limit (which seems a bit inaccurate to me).