On Mon, 2009-06-22 at 20:24 +0200, Lennart Poettering wrote:
Maybe I did not frame the question correctly: if the system has been
configured on purpose by the administrator to grant !SCHED_OTHER by
using RLIMIT_RTPRIO, why does rtkit have to mess with processes that it
did not grant privileges to?
> Even if some folks seem to believe it, I am not replacing anything
I understand that as well. If I may disagree, the long term implication
of rtkit is not just helping a few desktopish cases. It may be why it
was written. But if successful, it will be the only way a distribution
will grant !SCHED_OTHER out of the box, so it will affect anything that
wants to run !SCHED_OTHER out of the box in that distribution (say,
Fedora), including, for example, jack & friends. Thus my concerns and
(yes, I understand RLIMIT_RTPRIO will still be there, the system will
just not be configured out of the box to grant any access through that
> Really, I am doing my best to ease adoptions for those interested.
Sorry but that is not what I understood from your answer. Fons asked:
> * Question: is the 'demoting' of RT-threads applied only to RT
Note the part about "including those created by processes running as
root". Your answer:
> It can do both. resetting all is the default.
To my eyes "resetting all" would mean to _include_ processes running as
root, thus my remark.
Linux-audio-dev mailing list