On Tue, 2009-06-23 at 13:12 -0400, Paul Davis wrote:
yes, sorry, I was briefly swallowed into the rtkit-world :-) ...
> which are intended to guarantee that an uncontrollable fork bomb or
I don't know either, hopefully yes.
> to explain why this mechanism
This is what Lennart wrote in his original announcement:
> Why not use cgroups for this? Because it's simply a horrible API, and
Do you have any idea what containers are? No clue here...
It would seem to me that sched-rt-groups (with cgroup support) does
address the problem, but differently. SCHED_RESET_ON_FORK would prevent
the creation of a rt fork bomb, sched-rt-groups + cgroups would just
contain it within the boundaries of the maximum rt time alloted to that
All other issues remain the same (ie: what to do in userland when a
process _is_ eating cpu like crazy). Right?
Yes another issue that has not been raised or explained in the thread
> * Client authorization is verified with PolicyKit
What is verified? User account? Other stuff?
Linux-audio-dev mailing list