systemd: allow AF_NETLINK when upnp is enabled#2525
Conversation
|
Bad commit message |
|
Where is the guideline for good commit message? :p |
|
Rule of thumb: if the PR contains text that is missing in your commit message, then your commit message must be obviously bad. Second rule of thumb: if your commit message describes only what is obvious enough by looking at the diff, but doesn't even try to explain why, it's bad. |
|
Your commit message says "when upnp is enabled" but that's not what your actual code does - it checks whether the feature is not disabled. That's different from the existing smbclient check, and that has a bad smell. That needs to be explained. |
This is wrong. It's a |
|
Explanation still missing. |
mpd.service will fail to start when mpd is configured with upnp database/neighbor plugin and AF_NETLINK is not allowed in RestrictAddressFamilies=
|
Besides, multiple values of this option can end up enabling the upnp plugin, with the logic to determine that in src/lib/upnp/meson.build. So I guess that the best way to verify for sure that upnp is enabled is to check the configuration variable set in this file. |
AF_NETLINKis also needed for the upnp database plugin: https://bbs.archlinux.org/viewtopic.php?id=310134