mpdas can't connect to mpd about mpdas

[dglava]

I've narrowed it down a bit: commit f4e248a.

If I remove the global config file /etc/mpdasrc then it works again with the latest build from master. Anything up to that commit used to work even with the global config not removed from /etc.

Seems like the "global" config file in /etc has priority over the user config file in ~/.config/. I guess a potential fix for this would be prioritizing the "user" config files and only then loading the file in /etc.

[hrkfdn]

IIRC the global config is loaded first and then the user config, so any values set in the user config should overtop the global values.

[dglava]

I think the problem is when some values aren't set (or are commented out) in the user config file, then the ones from the global config file are taken. One must explicitly set the values in the user config file.

One problem might be the mpdpassword option. In my case, since I don't use it, mpdas failed to start, because it was set in the global config, but not in my user's config. I think that's why it wasn't able to connect.

[hrkfdn]

Which distribution is this? Does it install the example file in /etc? Does setting it to "" (empty value) work?

[dglava]

I am using Arch Linux, but packaged myself since it's not in the official repository.
I am using the latest build from master. It installs the sample config in /etc.

Just tried setting it to "" in the config file in /etc and it's not working; mpdas can't connect if I set host = "".

I guess a solution would be to make it disregard the config options from /etc or ~/.mpdasrc if the options from ~/.config/mpdasrc are loaded.

[hrkfdn]

For host an empty value is invalid. The default value is localhost.

[dglava]

Okay, I just set all the values explicitly in my user config file and it's working regardless of what's in the example/global config file.

My bad, I guess it's solved now.