What you're coming up against is a systemd feature called 'socket activation'. Address and port are opened not by mpd but by systemd on system startup, while mpd is only started when an actual connection request to that address and port is received. Hence those values have to be specified as part of the mpd.socket unit.
This is not a bug, but normal behaviour in a systemd world. Since mpd 0.19.10-1, the package-provided /etc/mpd.conf contains a note about this. I don't know if the systemd API makes it easy to query the address and port used for socket activation, so that mpd could log a helpful warning when those differ from mpd.conf. That would certainly be a nice feature. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639544 Title: mpd ignores the "port" in config by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpd/+bug/1639544/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
