On Tue, Jun 23, 2009 at 4:15 PM, Fernando
you are right. my initial reading was that "root group" in this
context had little to do with "root" in the traditional sense of uid=0
and more to do with "root of the filesystem" i.e. the root group is
the parent of all other cgroups. but it goes on to say "Therefore you
will not be able to run realtime tasks as any user other than root
until you have done that, even if the user has the rights to run
processes with realtime priority!"
i am also a little confused by what the default values mean (run time = 0)
> The document provides two ways of reallocating realtime real state
true, but what i actually meant was that the measurement and limit
system is in place with or without cgroups.
the API looks entirely usable to me, in the sense that i could easily
imagine a GUI control panel for this that would be comprehensible to
> Hmmm, did Lennart specifically answer the issue of the clone bomb? I
i believe he claimed the watchdog deals with this. it was pointed
out that all you need to do is to know the rule the watchdog uses and
you can still pretty effectively lock the machine from the perspective
of a non-CS-y user.
here's my halfway (?) summary:
"distros refuse to even provide a way to enable RLIMIT_RTPRIO because
it enables regular users to lockup the machine.
Up next: 8 other ways for regular users to easily lockup the machine ... "
> I don't know either. In either case the watchdog would probably be
I don't believe that the RTKit watchdog (like Kjetil's Das Watchdog)
takes any action against any SCHED_OTHER process.
Linux-audio-dev mailing list