You are not logged in.
- Topics: Active | Unanswered
#1 2017-03-26 00:09:13
- emacsomancer
- Member
- Registered: 2014-09-20
- Posts: 211
mpd systemd unit broken (after some 25 Mar update)? - w/ workaround
My mpd service completely failed in the middle of playing, about an hour after an update. I tried rebooting, but that did nothing.
Found that I could manually start it with:
/usr/bin/mpd --stdout --no-daemon --verbose /home/emacsomancer/.config/mpd/mpd.conf`systemctl status mpd.service` revealed:
[/usr/lib/systemd/system/mpd.service:25] Unknown lvalue 'RestrictNamespaces' in section 'Service'If I then commented out the two Restrict.... lines in /usr/lib/systemd/system/mpd.service as follows:
# more paranoid security settings
NoNewPrivileges=yes
ProtectKernelTunables=yes
ProtectControlGroups=yes
ProtectKernelModules=yes
# AF_NETLINK is required by libsmbclient, or it will exit() .. *sigh*
#RestrictAddressFamilies=AF_INET AF_INET6 AF_UNIX AF_NETLINK
#RestrictNamespaces=yes Then the systemd mpd.service would work again.
Last edited by emacsomancer (2017-03-26 00:12:19)
Offline
#2 2017-03-26 07:04:07
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,253
Re: mpd systemd unit broken (after some 25 Mar update)? - w/ workaround
Offline
#3 2017-03-26 15:55:14
- emacsomancer
- Member
- Registered: 2014-09-20
- Posts: 211
Re: mpd systemd unit broken (after some 25 Mar update)? - w/ workaround
Yeah, I saw that, but I'm not running the 32bit architecture.
Offline
#4 2017-03-26 16:30:20
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,253
Re: mpd systemd unit broken (after some 25 Mar update)? - w/ workaround
It's rather that the feature caused trouble on 32bit, thus was revoked, leaving services which had already incoporated it broken. Afaiu the feature is re-available w/ systemd 233
Offline