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: Sun, 28 May 2017 17:44:58 +0200 [thread overview]
Message-ID: <87r2z9rnnp.fsf@gnu.org> (raw)
In-Reply-To: <87efvdspuq.fsf@jamestechnotes.com> (James Richardson's message of "Wed, 24 May 2017 21:10:53 -0400")
James Richardson <james@jamestechnotes.com> skribis:
> Ludovic Courtès writes:
[...]
>>> Hmm, I move the key pair to /tmp and set the perms to 644 and offloading
>>> works for my regular user... Not quite sure I understand why.
>>
>> The ‘guix offload’ command is invoked by guix-daemon as root. So when
>> it is invoked, (getenv "HOME") returns "/root" or similar. Could that
>> be the problem?
>>
>> HTH,
>> Ludo’.
>
> Well, I think there is an issue with the offload. I don't (yet) know
> guile well enough to understand the code to help :(
OK.
> Here is what I am finding: $ guix build blah seems to offload builds
> properly. $ guix package -i blah, guix package -u blah, and $ guix
> system reconfigure config.scm does not offload builds.
Without more info, it’s hard to tell, but there are derivations that are
marked as “non-offloadable”, essentially because it’d take more time to
transfer them and build them remotely than to build them locally. Among
those derivations are profiles (built by ‘guix package’) and many of the
small items built by ‘guix system’. It could explain what you’re
seeing.
Something like ‘guix build libreoffice --no-substitutes’ should be
offloaded, provided --max-jobs is appropriate as discussed before.
HTH,
Ludo’.
prev parent reply other threads:[~2017-05-28 15:45 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
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 [this message]
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=87r2z9rnnp.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).