On 23.04.2023 18:20, mh@mike.franken.de wrote:
On Sonntag, 23. April 2023 17:11:38 CEST Andrei Borzenkov wrote:
On 23.04.2023 16:56, mh@mike.franken.de wrote:
Hi,
thx for the detailed description, but probably I couldn't make clear, where my problem really is. Its not about pipewire - I only wanted to say, that for pipewire I found the only snippets of documentation for rtkit. Instead I wanted to know, how to configure rtkit for other applications like Citrix Workspace.
You cannot "configure rtkit for other applications". rtkit-daemon listens on requests over D-Bus and fulfills (or denies) these requests. If your application does not talk to rtkit-daemon, there is nothing you can do from the rtkit side.
the application is using rtkit according to the journal entries. I just wanted to know, if *I* can configure something to optimize this usage.
You can set rtkit-daemon options that are described in README and you can change real time priority and/or allowed time before process get preempted via limits.conf for users and system.conf/service unit for services.
If your application does request to become real time but request is denied, we could look why.
This seems to indicate, that at least something is working:
tkit-daemon[5215]: Successfully made thread 17006 of process 17002 owned by '10000' RT at priority 5.
And process 17002 is your Citrix Workspace?
This is the only warning I get:
"rtkit-daemon[5215]: Warning: Reached burst limit for user '10000', denying request."
That can be changed by rtkit-daemon options (--actions-burst-sec/--actions-per-burts-max). Although the first question should probably be, why there are so many requests (default is 25 actions in 20 seconds).