bug#23274: Misleading error message when running guix-daemon as unprivileged user

2017-12-11 Thread Ludovic Courtès
Hi Martin, Martin Castillo skribis: >> “Address already in use” makes me directly think that there is already >>another daemon running. > > This was in response to OP, saying that I don't think that needs to be > changed. > > The rest was about testing it with root and I (half) expected an erro

bug#23274: Misleading error message when running guix-daemon as unprivileged user

2017-12-11 Thread Martin Castillo
Hi, I could have expressed myself more clearly. > “Address already in use” makes me directly think that there is already >another daemon running. This was in response to OP, saying that I don't think that needs to be changed. The rest was about testing it with root and I (half) expected an err

bug#23274: Misleading error message when running guix-daemon as unprivileged user

2017-12-11 Thread Ludovic Courtès
Hi Martin, Martin Castillo skribis: > “Address already in use” makes me directly think that there is already > another daemon running. Strangely, starting another daemon as root > works. It seems to take the socket from the other daemon away. Is this > intended? Or can two daemons run in paralle

bug#23274: Misleading error message when running guix-daemon as unprivileged user

2017-12-09 Thread Martin Castillo
Hi, “Address already in use” makes me directly think that there is already another daemon running. Strangely, starting another daemon as root works. It seems to take the socket from the other daemon away. Is this intended? Or can two daemons run in parallel without problems? What is your use case

bug#23274: Misleading error message when running guix-daemon as unprivileged user

2016-04-11 Thread Leo Famulari
When trying to start the guix-daemon as an unprivileged user, the following error message is printed: error: cannot bind to socket `/var/guix/daemon-socket/socket': Address already in use Would it make sense to try to provide a more helpful error message?