From: ludo@gnu.org (Ludovic Courtès)
To: James Richardson <james@jamestechnotes.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: offload daemon
Date: Tue, 23 May 2017 22:33:54 +0200 [thread overview]
Message-ID: <871srf9utp.fsf@gnu.org> (raw)
In-Reply-To: <8737bv601k.fsf@jamestechnotes.com> (James Richardson's message of "Tue, 23 May 2017 11:54:47 -0400")
Hello,
James Richardson <james@jamestechnotes.com> skribis:
> I am trying to setup an offload daemon.
>
> I have everything setup correctly (I think ;)
>
> $ guix offload test completes successfully.
>
> The offload daemon is actually guix on a foreign distro (Debian sid in
> this case).
>
> Neither guix running on top of a Debian (sid and jessie) nor guixsd seem
> to even call out to the offload daemon. All boxen are 64.
>
> My /etc/guix/machines.scm is here
>
> (list (build-machine
> (name "thor.lab01.jamestechnotes.com")
> (system "x86_64-linux")
> (host-key "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJf0ezYgeVFit40VJwaBEW1dGm2Xz+SHzVmib8IbN58y root@thor")
> (user "guix")
> (speed 1.)
> (private-key
> (string-append (getenv "HOME")
> "/.ssh/identity-for-guix"))))
>
> Is x86_64-linux the proper system type?
Yes.
There are several things to consider here. By default, guix-daemon
creates a single job, so that single job will end up being built
locally, unless you spawn, say, two “guix build” commands in parallel
(the number of jobs is per client.)
Running “guix-daemon --max-jobs=0” should force all builds to be
offloaded:
https://www.gnu.org/software/guix/manual/html_node/Invoking-guix_002ddaemon.html
I *think* “guix build --max-jobs=0” should give the same result.
Alternately, if you run “guix build --max-jobs=2”, presumably half of
the builds will be offloaded.
Let us know if that works for you.
Ludo’.
next prev parent reply other threads:[~2017-05-23 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 15:54 offload daemon James Richardson
2017-05-23 20:33 ` Ludovic Courtès [this message]
2017-05-24 1:36 ` James Richardson
2017-05-24 2:14 ` James Richardson
2017-05-24 10:10 ` Ludovic Courtès
2017-05-25 1:10 ` James Richardson
2017-05-28 15:44 ` 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=871srf9utp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=james@jamestechnotes.com \
/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.
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).