[Pkg-mpd-maintainers] Bug#993359: Update systemd unit to raise memlock limit for io_uring support
Geoff
efrim at azylum.org
Tue Aug 31 13:26:26 BST 2021
Hi Micha !
31/08/2021, MichaIng wrote:
> The memlock limit can be raised via systemd unit, which has been done
> upstream: https://github.com/MusicPlayerDaemon/MPD/blob/v0.22.x/systemd/system/mpd.service.in#L19-L20
> But this change obviously wasn't applied to the Debian package.
Systemd unit file used in the package comes from upstream with a minor patch [0].
Then I'm pretty sure LimitMEMLOCK config is present in bullseye MPD 0.22.6-1.
I just made a plain install of bullseye (amd64 VM), here is what I got:
$ systemctl cat mpd.service | grep LimitMEM
LimitMEMLOCK=64M
$ systemctl show mpd.service | grep LimitMEM
LimitMEMLOCK=67108864
LimitMEMLOCKSoft=67108864
I did not reproduce the “Failed to initialize io_uring” error either.
I confused here, please have a look at /usr/lib/systemd/system/mpd.service,
LimitMEMLOCK should be there on a vanilla install.
Do you have any fragments in /etc/systemd/system/mpd.service.d that could interfere?
Cheers
k
[0] https://sources.debian.org/src/mpd/0.22.6-1/systemd/system/mpd.service.in/
More information about the Pkg-mpd-maintainers
mailing list