I just fixed a situation where I couldn't get mpd to work over my home network.
I think it may be this same issue.
On my system
# sysctl net/ipv6/bindv6only
net.ipv6.bindv6only = 1
netstat would show init listening on [::]:6600 but doesn't report the
IPV6_V6ONLY socket state so I had
On martes, 13 de septiembre de 2016 12:45:17 A. M. ART Florian Schlichting
wrote:
> On Mon, Sep 12, 2016 at 06:36:00PM -0300, Lisandro Damián Nicanor Pérez
Meyer wrote:
> > I expect that, if the daemon is not running and a client tries to connect
> > to port 6600 then systemd will start the
On Mon, Sep 12, 2016 at 06:36:00PM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> 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.
yes, and that works for me.
1) There is
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
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
5 matches
Mail list logo
