From b4be094be8d9367c559692aac4d39d19f0c47b73 Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Fri, 5 Jan 2024 10:22:28 +0100 Subject: [PATCH] doc: clarify rlimits conf file Fixes #3760 --- src/modules/module-rt/25-pw-rlimits.conf.in | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/src/modules/module-rt/25-pw-rlimits.conf.in b/src/modules/module-rt/25-pw-rlimits.conf.in index 4714d7e5a..9b951a27e 100644 --- a/src/modules/module-rt/25-pw-rlimits.conf.in +++ b/src/modules/module-rt/25-pw-rlimits.conf.in @@ -1,7 +1,13 @@ # This file was installed by PipeWire project for its libpipewire-module-rt.so -# It's believed to be acceptable to have match rules that will never be true -# i.e. a group that does not exist. +# It is up to the distribution/user to create the @MATCH@ 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. # @MATCH@ - rtprio @RTPRIO@ @MATCH@ - nice @NICE@