Re: [mpd-devel] systemd and zeroconf: No global port, disabling zeroconf

2014-12-03 Thread Punky
Thanks Max, Thus, MPD currently does not enable zeroconf when socket activation is used, because MPD does not know what port to announce. I understand this now. systemd would activate the socket on behalf of the service because you told it to. It is optional, and you enabled it (systemctl

Re: [mpd-devel] systemd and zeroconf: No global port, disabling zeroconf

2014-12-02 Thread Punky
Hi Max and all, On Wed, Dec 3, 2014 at 4:39 AM, Max Kellermann m...@duempel.org wrote: listen_systemd_activation() is true. Then the function exit immediately without setting listen_port = port. Correct. Which value do you expect it to have, and where will it obtain that value from?

Re: [mpd-devel] systemd and zeroconf: No global port, disabling zeroconf

2014-12-02 Thread Max Kellermann
On 2014/12/03 02:56, Punky punky...@gmail.com wrote: In zeroconf module, listen_port variable is used. listen_port variable should be set to the value that MPD (successfully) listens to, and if TCP port (default 6600) is being configured But listen_port is ignored when systemd socket