Re: System-wide PulseAudio instance with realtime priority as non-root from systemd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


What happens if you start the pulseaudio daemon in the console? Do you get rt scheduling then? I would check that first to see if pulsesudio is configured correctly. If that works you're probably better off asking the question in the systemd list then...

Best regards, Jürgen

Am 31. Oktober 2020 01:33:05 schrieb Matt Garman <matthew.garman@xxxxxxxxx>:

It appears it was a systemd config issue, rather than an issue with
pulse.  In addition to updating /etc/security/limits.conf, I also
needed to add the following to the [Service] stanza in my pulseaudio
service file:


But I still cannot get realtime (fifo) scheduling to work.  I
additionally have this in my Service stanza:


And this in /etc/pulse/daemon.conf:

realtime-scheduling = yes

But still not getting realtime priority:

# chrt -p `pgrep pulseaudio`
pid 1203's current scheduling policy: SCHED_OTHER
pid 1203's current scheduling priority: 0


On Fri, Oct 30, 2020 at 5:35 PM Matt Garman <matthew.garman@xxxxxxxxx> wrote:

On Fri, Oct 30, 2020 at 5:17 PM Jürgen Herrmann <t-5@xxxxxx> wrote:
Look here:

Hi Jürgen, thank you for the quick reply.  But either I'm missing
something, or that says to do exactly what I've already done..
Realtime scheduling works when run from the commandline using
"runuser" (i.e. so I don't run as root).  But when launched from
systemd, setting the realtime priority fails (setrlimit() operation
not permitted).

Thanks again,
pulseaudio-discuss mailing list

Mit Aqua Mail Android

pulseaudio-discuss mailing list

[Index of Archives]     [Linux Audio Users]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux