From: Michael Rohleder <mike@rohleder.de>
To: Emmanuel Medernach <emmanuel.medernach@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Few questions
Date: Tue, 12 May 2020 11:49:18 +0200 [thread overview]
Message-ID: <87lflxsctd.fsf@rohleder.de> (raw)
In-Reply-To: <CAC_pKx9OwELG2S7oQrJ4TVUisyV7pQg+t7r_8xD7b7-3_E7SVw@mail.gmail.com> (Emmanuel Medernach's message of "Tue, 12 May 2020 11:30:19 +0200")
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
Emmanuel Medernach <emmanuel.medernach@gmail.com> writes:
>> > - How to replace /tmp during build with another partition to avoid
>> filling
>> > it ?
>>
>> I do not know.
>>
>>
> Or could it be added as an installation option ?
From the manual (2.5):
"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."
If you are on a foreign distro, you can add
export TMPDIR="/yourBigAndFastDisk"
to the init/start script of the guix-daemon.
If you are on a guix system (or guix generated vm etc), you can add
(service guix-service-type
(guix-configuration
(tmpdir "/yourBigAndFastDisk")))
to your services.
--
I've finally learned what "upward compatible" means. It means we get to
keep all our old mistakes.
-- Dennie van Tassel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-05-12 9:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 7:22 Few questions Emmanuel Medernach
2020-05-12 8:04 ` zimoun
2020-05-12 9:30 ` Emmanuel Medernach
2020-05-12 9:49 ` Michael Rohleder [this message]
2020-05-12 11:40 ` zimoun
2020-05-12 11:55 ` Emmanuel Medernach
2020-05-12 12:04 ` zimoun
2020-05-13 6:15 ` Emmanuel Medernach
2020-05-14 11:32 ` Tobias Geerinckx-Rice
2020-05-14 11:34 ` Tobias Geerinckx-Rice
2020-05-14 12:08 ` Emmanuel Medernach
2020-05-14 12:30 ` Tobias Geerinckx-Rice
2020-05-14 12:17 ` zimoun
2020-05-14 12:35 ` Julien Lepiller
2020-05-14 12:39 ` zimoun
2020-05-14 13:56 ` Julien Lepiller
2020-05-14 14:17 ` zimoun
2020-05-14 14:26 ` Tobias Geerinckx-Rice
2020-05-14 12:36 ` Tobias Geerinckx-Rice
2020-05-14 10:24 ` Vincent Legoll
2020-05-12 9:41 ` pelzflorian (Florian Pelz)
2020-05-12 9:57 ` Emmanuel Medernach
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=87lflxsctd.fsf@rohleder.de \
--to=mike@rohleder.de \
--cc=emmanuel.medernach@gmail.com \
--cc=help-guix@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.
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).