Hi Fons, On December 27, 2017 1:59:17 PM GMT+01:00, Fons Adriaensen <fons@xxxxxxxxxxxxxx> wrote: >On Wed, Dec 27, 2017 at 12:56:16PM +0100, David Runge wrote: > >> >On 27 December 2017 at 04:39, David Runge <dave@xxxxxxxxxxx> wrote: >> >> Addditionally, it should create the system group realtime (using >> >> systemd-sysusers), to decouple the realtime priorities from the >audio >> >> group. > >I'm not sure this is a good idea. > >There is no reason why application classes that require realtime >or locked memory (audio, video, sdr,...) should all have the same >limits. > >The way limits.conf works is that you can have any matrix of >users/groups vs. limits. Accessing each individual limit (e.g. >realtime) only via a single dedicated group (which seems to be >the underlying idea) takes away that degree of freedom. This is actually how it has been done by packaging jack/jack2 [1] [2] for years in accordance to upstream documentation on the topic [3]. As you can see in the first two links, this has been bound to the "audio" group, that is also used by alsa for device permissions. Do you have an alternative suggestion that is packageable? Best, David [1] https://git.archlinux.org/svntogit/community.git/tree/trunk/40-hpet-permissions.rules?h=packages/jack2 [2] https://git.archlinux.org/svntogit/community.git/tree/trunk/99-audio.conf?h=packages/jack2 [3] http://jackaudio.org/faq/linux_rt_config.html -- https://sleepmap.de
