Over the past years I religiously , when new install, I edited / added in /etc/security limits.conf or added 99-realtime according to How do I configure my linux system to allow JACK to use realtime scheduling
The above , so my understanding , is valid to all Linux flavours.
I changed over to Suse Tumbleweed which has a pipewire implementation.
Limits.conf was not (any more) under /etc/security but was moved to /usr/etc/secutrity.
I wonder if that was done in agreement with all linux flavours.
Now I think I made a mistake whilst doing the change in /usr/etc/security assigning “audio”
but I could not loginto the system any longer even trying with run level I could not log in.
I let you know how go with it.
But, I thought it is important that you know about the change.
In Debian pipewire creates a file /etc/security/limits.d/25-pw-rlimits.conf
Isn’t that the case in Suse?
# This file was installed by PipeWire project for its libpipewire-module-rt.so
# It is up to the distribution/user to create the @pipewire group and to add the
# relevant users to the group.
#
# PipeWire will fall back to the RTKit DBus service when the user is not able to
# acquire RT priorities with rlimits.
#
# If the group is not automatically created, the match rule will never be true
# and this file will have no effect.
#
@pipewire - rtprio 95
@pipewire - nice -19
#@pipewire - memlock 4194304
@pipewire - memlock unlimited
