From: Roel Janssen <roel@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 27426@debbugs.gnu.org
Subject: [bug#27426] [PATCH 0/2] 'guix-daemon --listen' can specify multiple interfaces
Date: Tue, 20 Jun 2017 15:28:37 +0200 [thread overview]
Message-ID: <rbu1sqeaiuy.fsf@gnu.org> (raw)
In-Reply-To: <rbu37auall1.fsf@gnu.org>
Roel Janssen writes:
> Hi Ludo’,
>
> Ludovic Courtès writes:
>
>> Hello Guix!
>>
>> Commit 3dff90ce34448551bc82a6a7262837c0561a4691 added support for
>> guix:// URIs on the client side. This commit adds guix-daemon support
>> to specify TCP sockets to listen to, like this:
>>
>> # Listen on the loopback interface only, port 1234.
>> guix-daemon --listen=localhost:1234
>>
>> # Listen on the Unix-domain socket and on the public interface,
>> # port 44146.
>> guix-daemon --listen=/var/guix/daemon-socket/socket \
>> --listen=0.0.0.0
>>
>> The primary use case is clusters running a single ‘guix-daemon’ instance
>> that can be accessed from other nodes on the local network.
>>
>> Feedback welcome!
>
> Thanks a lot for these patches! Today I tried to run the guix-daemon
> with it on our cluster. It works fine, except for the following (which
> might be unrelated):
>
> [root@hpcguix ~]$ /gnu/repositories/guix/guix-daemon --listen=/gnu/daemon-socket/socket --listen=<ip-address>:<port> ...
>
> [roel@submit-node1 ~]$ guixr package -i samtools
> The following package will be installed:
> samtools 1.3.1 /gnu/store/syl74az7a5mw5f8r5jfldiddlyc3ry28-samtools-1.3.1
>
> substitute: error: executing `/usr/local/libexec/guix/substitute': No such file or directory
> guix package: error: build failed: substituter `substitute' died unexpectedly
>
Ooh, nevermind.. This has to do with the 'pre-inst-env' script.
>
> When passing --no-substitutes, the command works, which means the
> guix-daemon with these patches applied does what we expect.
>
> Note that, I could've used 'guix' instead of 'guixr', but all 'guixr'
> essentially does is set the GUIX_DAEMON_SOCKET and GUIX_PACKAGE_PATH
> variables.
>
> I wonder where this /usr/local/libexec comes from, and how/where I can
> configure it so that it works the same as before.
>
> Thanks again for these patches.
>
> Kind regards,
> Roel Janssen
next prev parent reply other threads:[~2017-06-20 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 16:03 [bug#27426] [PATCH 0/2] 'guix-daemon --listen' can specify multiple interfaces Ludovic Courtès
2017-06-19 16:04 ` [bug#27426] [PATCH 1/2] store: Define a default port for TCP connections Ludovic Courtès
2017-06-19 16:04 ` [bug#27426] [PATCH 2/2] daemon: '--listen' can be passed several times, can specify TCP endpoints Ludovic Courtès
2017-06-20 12:29 ` [bug#27426] [PATCH 0/2] 'guix-daemon --listen' can specify multiple interfaces Roel Janssen
2017-06-20 13:28 ` Roel Janssen [this message]
2017-06-20 14:08 ` Ludovic Courtès
2017-06-20 15:15 ` Roel Janssen
2017-06-22 9:02 ` bug#27426: " Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rbu1sqeaiuy.fsf@gnu.org \
--to=roel@gnu.org \
--cc=27426@debbugs.gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).