[Pkg-mpd-maintainers] Bug#813754: Bug#813754: Bug#813754: Can't open port 6600 when run syste, -wide vis systemd

Lisandro Damián Nicanor Pérez Meyer perezmeyer at gmail.com
Mon Sep 12 21:36:00 UTC 2016


Control: tag -1 - moreinfo

On lunes, 12 de septiembre de 2016 10:50:00 P. M. ART Florian Schlichting 
wrote:
> Hi Lisandro,

Hi!
 
> back in February you reported #813754 against mpd, claiming it would not
> open port 6600 if started via systemd.
> 
> I just re-read our email exchange, and I think you'were just confused
> about how systemd socket activation works. 

I expect that, if the daemon is not running and a client tries to connect to 
port 6600 then systemd will start the daemon and the client wouldn't even 
notice it.

That's not happening.

If I'm still wrong in my expectations about systemd and sockets, please read 
below at least to understand what I see as a bug.

> netstat output doesn't show
> "mpd", but everything still works as one would expect, no?

No, the client can't reach the server unless I start mpd as described in the 
bug.

> Please confirm that #813754 doesn't need to be kept open, or else please
> describe what is not working for you?

I would expect turning on my machine, fire my mpd android client app and enjoy 
music :) But I'm getting a client that can't connect to the server unless I 
start mpd as described in the bug.

-- 
Gabardinas "Windows 95". Se cuelgan solas.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-mpd-maintainers/attachments/20160912/b597a9b8/attachment-0001.sig>


More information about the Pkg-mpd-maintainers mailing list