[LAD] [ANNOUNCE] Safe real-time on the desktop by default; Desktop/audio RT developers, read this!

Fernando Lopez-Lezcano nando at ccrma.Stanford.EDU
Tue Jun 23 00:34:15 UTC 2009


On Tue, 2009-06-23 at 01:53 +0200, Lennart Poettering wrote:
> On Mon, 22.06.09 16:33, Fernando Lopez-Lezcano (nando at ccrma.Stanford.EDU) wrote:
> 
> > If rtkit would demote all processes when triggered, regardless of whether 
> > rtkit granted the privileges or not then I can't really bypass it, it is 
> > always there defining policy. 
> 
> Except that rtkit wouldn't be started in the first place if the apps
> get RT by some other means, since rtkit is only the last resort for them.

Sorry to be a pest, if only _one_ app requests through rtkit then all
bets are off until a logout/login sequence, right? 

> But really, if this is so important to you then we can certainly
> change that. 

I happen to think it is the wrong thing to do in general: you are
essentially forcing policy for something you don't have complete control
over, so that it may overlap or override with what other methods want.
It is probably going to create problems in the long run, but that is a
very non-scientific thing to say. 

(BTW, I still have to try to figure out if jack support is possible -
don't know when I'm going to have time - jack bestows rt on threads that
the client programs use, but not through a fork)

-- Fernando





More information about the Linux-audio-dev mailing list