From: ludo@gnu.org (Ludovic Courtès)
To: Andrei Osipov <andrspv@gmail.com>
Cc: 19771-done@debbugs.gnu.org
Subject: bug#19771: Missing documentation on enviroment variables for guix-deamon
Date: Sat, 07 Feb 2015 18:42:28 +0100 [thread overview]
Message-ID: <87wq3toby3.fsf@gnu.org> (raw)
In-Reply-To: <87d25py8yj.fsf@gmail.com> (Andrei Osipov's message of "Wed, 04 Feb 2015 18:47:48 +0300")
Andrei Osipov <andrspv@gmail.com> skribis:
> <andreoss`> how to change the temporary directory from /tmp to /var/tmp?
> [08:14]
> <andreoss`> i have /tmp as tmpfs and it has no enough space to build gcc
> <Sleep_Walker> hm, I can't find it either in ./configure, either as parameter
> to guix-daemon [08:29]
> <Sleep_Walker> it seems it could respect TMPDIR environment variable [08:34]
> <Sleep_Walker> andreoss`: could you confirm? [08:36]
> <Sleep_Walker> export TMPDIR=/var/tmp ; guix-daemon <your_parameters>
> <andreoss`> Sleep_Walker: confirmed [08:39]
I’ve added two paragraphs to that effect:
When the daemon performs a build on behalf of the user, it creates a
build directory under ‘/tmp’ or under the directory specified by its
‘TMPDIR’ environment variable; this directory is shared with the
container for the duration of the build. Be aware that using a
directory other than ‘/tmp’ can affect build results—for example, with a
longer directory name, a build process that uses Unix-domain sockets
might hit the name length limitation for ‘sun_path’, which it would
otherwise not hit.
The build directory is automatically deleted upon completion, unless
the build failed and the client specified ‘--keep-failed’ (*note
‘--keep-failed’: Invoking guix build.).
Thanks for the report!
Ludo’.
prev parent reply other threads:[~2015-02-07 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 15:47 bug#19771: Missing documentation on enviroment variables for guix-deamon Andrei Osipov
2015-02-07 17:42 ` 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=87wq3toby3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=19771-done@debbugs.gnu.org \
--cc=andrspv@gmail.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.
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).