Control: tags 813754 +moreinfo
Hi Lisandro, 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. netstat output doesn't show "mpd", but everything still works as one would expect, no? Please confirm that #813754 doesn't need to be kept open, or else please describe what is not working for you? Florian On Tue, Feb 09, 2016 at 01:16:15AM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > On Monday 08 February 2016 21:21:20 you wrote: > > Hi Lisandro, > > > > > Hi! I use mpd on my personal machine as a system service, without > > > pulseaudio. > > > > > > I noticed that if I let mpd start via systemd port 6600 will not be > > > opened. > > > > mpd uses systemd's socket activation feature, as defined in > > /lib/systemd/system/mpd.socket, > > Correct. > > > so port 6600 should be open and you > > should see systemd listening there until the first connection is > > actually made. > > > > What is the netstat output after system startup? > > # netstat -putan | grep mpd > tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN > 721/mpd > > Nos I never though of grepping 6600: > > # netstat -putan | grep 6600 > tcp6 0 0 :::6600 :::* LISTEN > 1/init