On Thu, Jan 20, 2011 at 9:34 PM, <fons@kokkinizita.net> wrote:
After years of problems and frustration,for the last two or three years we (the people using such audio apps on Linux) have finally got a system that allows normal users to do this (using ulimits and just two lines in /etc/security/limits.conf giving members of the 'audio' group the required privileges).
So here's my question: will a system using systemd still allow this, *without* requiring source modifications to each and every application (to join a specific cgroup), and *whitout* every application requiring real-time or memory locks to be 'registered' somewhere ? As far as I've understood it would not. Which would make systemd an absolute no-go for users requiring this.
Note that grouping processes using cgroups does not imply having to use the group scheduler . IIRC systemd uses a debugging hierarchy by default which does not affect program resources.