From: Benjamin Slade <beoram@gmail.com>
To: "Clément Lassieur" <clement@lassieur.org>
Cc: help-guix@gnu.org
Subject: Re: Guix on aarch64
Date: Thu, 16 Aug 2018 11:33:38 -0600 [thread overview]
Message-ID: <87lg966wst.fsf@jnanam.net> (raw)
In-Reply-To: <878t565k85.fsf@lassieur.org>
Thanks, Clément. For some reason the `--build-users-group=guixbuild`
make me think it was supposed to build something. In retrospect, it's
obvious that it's just a groupname.
So far it seems to be working. I'll have to see if I can get runit to
start the guixdaemon automatically.
> > `# ~root/.guix-profile/bin/guix-daemon --build-users-group=guixbuild`
> >
> > It just seems to hang. When I look at the process, it doesn't seem to be
> > using cpu resources anything. I tried leaving it for a couple of hours,
> > but it never seems to do anything.
> It is its normal behaviour, because it's a long-running process; it
> should be always running and the Guix command talks to it. People
> usually use an init manager to start it automatically (systemd, the
> Shepherd...). You can also add '&' at the end of the command so that it
> goes in the background.
> Clément
thanks again,
—Ben
--
Benjamin Slade - https://babbagefiles.xyz
`(pgp_fp: ,(21BA 2AE1 28F6 DF36 110A 0E9C A320 BBE8 2B52 EE19))
'(sent by mu4e on Emacs running under GNU/Linux . https://gnu.org )
`(Choose Linux ,(Choose Freedom) . https://linux.com )
next prev parent reply other threads:[~2018-08-16 17:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 15:27 Guix on aarch64 Benjamin Slade
2018-08-16 16:50 ` Clément Lassieur
2018-08-16 17:33 ` Benjamin Slade [this message]
2018-08-16 17:41 ` Benjamin Slade
2018-08-20 17:51 ` Mark H Weaver
2018-08-21 3:52 ` Benjamin Slade
2018-08-21 4:38 ` Leo Famulari
2018-08-21 5:20 ` Benjamin Slade
2018-08-21 17:44 ` Mark H Weaver
2018-08-21 21:31 ` Benjamin Slade
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=87lg966wst.fsf@jnanam.net \
--to=beoram@gmail.com \
--cc=clement@lassieur.org \
--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).