[PlanetCCRMA] the jack permissions conundrum

[Fernando Lopez-Lezcano]

On Tue, 2010-05-25 at 09:39 -0700, Niels Mayer wrote:
> On Mon, May 24, 2010 at 9:08 PM, Simon Lewis
> <simon.lewis at slnet-online.de> wrote:
> > Since the user should not need to manually edit conf files I would suggest to give all users rt-sscheduling as is the case now.
> 
> Further, these wildcards could end up matching and overriding other
> limits set for other programs. For example instead of running at
> priority 20 and nice -20 per:
> > ## Automatically appended by jack-audio-connection-kit
> > @pulse-rt - rtprio 20
> > @pulse-rt - nice -20
> 
> The wildcards could override the above pulseaudio settings, and end up
> mathcing the "*" and get priority 99 and nice -10.
> 
>  Which means that, for example, your pulseaudio RT could end up
> running at the exact same priority as Jack RT -- which is a good way
> to get a deadlock. Perhaps the  jack lockups I saw related to this are
> because jack and pulseaudio were running at the same priority (due to
> the wildcards), and when jack signals pulseaudio to shut itself off
> via dbus, they deadlock.

That would be very simple to verify. Install the Planet CCRMA Jack.
Restart the computer. See at what rt priority pulse is running. I doubt
you will see what you presume. 

-- Fernando