Hi, I have gone back working on this issue and I can confirm that the issue is due to the socket. It seems like this "socket" unit is disabling usage of a Unix socket in favor of a TCP socket. What do you recommend for someone who wants to use a UNIX socket? Should I edit the socket file in some way or simply disable it?
Regards, On Sat, Jan 04, 2020 at 04:17:24PM -0500, Simon Désaulniers wrote: > Dear contributors, > > To this day, I can't reproduce what I was talking about in my initial post. > Therefore, I assume that the issue resolved somehow. I can't say what changed > between those now and then and I think that we can close this issue. > > Regards, > > On Thu, Nov 07, 2019 at 11:34:03AM +0100, Florian Schlichting wrote: > > Hi Simon, > > > > On Tue, Oct 01, 2019 at 04:14:40PM +0200, kaliko wrote: > > > On Sun, 28 Jul 2019 17:14:08 -0400 Simon Désaulniers > > > <sim.desaulni...@gmail.com> wrote: > > > > […] > > > > After upgrading from 0.21.5-3 to 0.21.11-1, systemd's mpd service > > > > doesn't seem > > > > to use the UNIX socket configured from my mpd configuration located at > > > > /home/simon/.config/mpd/mpd.conf. > > > > […] > > > > > > I did not manage to reproduce the issue. > > > I'll try again later on a freshly installed VM upgraded to testing, but > > > so far I have > > > not been able to reproduce the issue (tested also with mpd 0.21.15). > > > > > > Maybe someone from MPD team is willing to give it a shot. > > > > with version 0.21.8, mpd gained a _user_ mpd.socket unit, which defines > > > > ListenStream=%t/mpd/socket > > ListenStream=6600 > > > > and is enabled by default. My feeling is that this is responsible for > > your observed differences between using systemctl and manually launching > > mpd. Did mpd.socket get stopped/restarted in your testing? > > > > HTH, > > Florian > > > > -- > Simon Désaulniers > sim.desaulni...@gmail.com -- Simon Désaulniers sim.desaulni...@gmail.com
signature.asc
Description: PGP signature
