Hi, On Mon, May 18, 2015 at 10:48:08AM +0200, Florian Schlichting wrote: > you're obviously using systemd to start mpd via socket activation. The > way systemd creates the socket and thus makes mpd available on the > network is not determined by the mpd configuration, but through the > systemd unit called mpd.socket, and mpd itself is not able to change the > settings made in the socket unit when it has actually been started, i.e. > the bind_to_address directive becomes ineffective with socket > activation. > > The default mpd.socket unit makes mpd available via both IPv4 and IPv6 > on all interfaces, so you'll likely want to customize the ListenStream > directive in a local copy.
Thanks for your hint, I found the file, changed the directive in question to ListenStream=localhost:6600 and probably through "systemctl reenable mpd.socket", I managed to apply the change. I guess I'm not systemd savvy :-) > I'm not sure if this classifies as "systemd > common knowledge" that we still need a little time to thoroughly grasp, > or if a helpful comment in the mpd sample configuration is called for? A comment would probably save this pitfall from some mpd users that have proviously only used non-systemd Debian. I guess "systemd common knowledge" isn't that common among Debian users yet (it might be just me, but I doubt it). Thanks, Jonathan
signature.asc
Description: Digital signature
