From: Mark H Weaver <mhw@netris.org>
To: Louis <guix@rcdrun.com>
Cc: help-guix@gnu.org
Subject: Re: Guix unmounted my /home, while -i hello
Date: Mon, 07 Mar 2016 20:59:06 -0500 [thread overview]
Message-ID: <87pov5hgr9.fsf@netris.org> (raw)
In-Reply-To: <20160307223914.GA10916@protected.rcdrun.com> (Louis's message of "Mon, 7 Mar 2016 23:39:15 +0100")
Louis <guix@rcdrun.com> writes:
> Yes, I have tried it again, and it happened again, on the
> second time I have sent a bug. It looks to me dangerous to
> try it third time.
I have only one idea what could cause something like this.
Did you add any users to the 'guix-builder' group other than the users
dedicated for that purpose? If so, that's a problem.
guix-daemon considers all of the users in that group to be exclusively
for its use. When asked to build something, it chooses a user from that
group to do the build, and then after the build it *kills* all processes
owned by that user.
Every once in a while, someone decides to add their normal user account
to that group, and discovers that after every build guix-daemon kills
all of their user processes. If you added more users to that group,
perhaps guix-daemon is killing some process that causes your encrypted
/home to become unmounted?
Mark
next prev parent reply other threads:[~2016-03-08 1:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 10:21 Guix unmounted my /home, while -i hello guix
2016-03-07 19:44 ` Andreas Enge
2016-03-07 22:39 ` Louis
2016-03-08 1:59 ` Mark H Weaver [this message]
2016-03-08 7:10 ` Louis
2016-03-08 18:27 ` guix
2016-03-09 15:41 ` Ludovic Courtès
2016-03-09 17:01 ` Louis
2016-03-09 18:13 ` guix
2016-03-10 16:29 ` Ludovic Courtès
2016-03-10 16:36 ` Jean Louis
2016-03-11 13:34 ` Ludovic Courtès
2019-10-09 6:26 ` Andreas, here is kind question to provide facts on your statements about RMS Jean Louis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pov5hgr9.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix@rcdrun.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.