Re: [Jack-Devel] jack - audio group - package install

PrevNext  Index
DateTue, 24 Jan 2012 13:47:32 -0800
From Fernando Lopez-Lezcano <[hidden] at ccrma dot Stanford dot EDU>
ToPaul Davis <[hidden] at linuxaudiosystems dot com>
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToPaul Davis Re: [Jack-Devel] jack - audio group - package install
Follow-UpFons Adriaensen Re: [Jack-Devel] jack - audio group - package install
On 01/24/2012 06:53 AM, Paul Davis wrote:
> On Tue, Jan 24, 2012 at 9:45 AM, Kaj Ailomaa<[hidden]>  wrote:
>
>> What bugs me is that you can install jack, but you won't get realtime
>> privilege doing so. It's an unnecessary step to administer groups. It's just
>> a strange thing to do.
>
> this is not a "universal truth". there are several distributions and
> overlays that automatically provide RT/memlock priviledges when
> installing JACK.
>
> the issue you're raising is important but because of the way linux
> "works" its a question for each distribution to solve in its own way.

Yes.

I think a near optimal solution (there are bound to be cases where this 
might be undesirable) would be to have SCHED_FIFO/RR permissions tied to 
the active login session[*]. I tried once to see how this might be done 
but failed (I was trying to use one of the many *kit thingies, I forget 
which).

Ideally you install an extra package that has a suitable configuration 
file and only users that login physically to the computer would be 
granted rt access and only during the duration of the login (if users 
are switched, permissions follow the currently active user, etc, etc).

In Planet CCRMA I have an additional small package that you install and 
gives everyone access to rt but that is considered by many an additional 
security risk (low IMO, but not zero).

-- Fernando

[*] if you don't have active login sessions you probably know enough 
linux to configure things manually so that it works - for standalone 
systems, for example
PrevNext  Index

1327441674.27723_0.ltw:2,a <4F1F26F4.80806 at localhost>