From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Pjotr Prins" <pjotr.public12@thebird.nl>
Cc: 32183@debbugs.gnu.org
Subject: bug#32183: New ‘guix pull’ /root/.config/current/bin/guix: Permission denied
Date: Tue, 11 Sep 2018 11:34:33 +0200 [thread overview]
Message-ID: <m1y3c89y3a.fsf@fastmail.net> (raw)
In-Reply-To: <87zhwq91dc.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
Hi Ludo,
> I don’t think you’re doing anything wrong. Could anyone of you who
> experience this problem strace guix-daemon? I’ve thought about this and
> don’t understand where that EACCES (“Permission denied”) comes from.
>
> Specifically, you’d have to run something along these lines as root:
>
> strace -f -p $(pidof guix-daemon) -o log
>
> and then, as root or non-root (it doesn’t matter), run, say:
>
> guix build curl -S --no-substitutes
The log file (compressed) is attached.
In doing this I noticed that I have two guix-daemon processes running:
root 1583 0.0 0.0 33156 2412 ? Ss 08:55 0:00 /root/.config/guix/current/bin/guix-daemon --build-users-group=guixbuild
root 13003 0.0 0.0 36028 6256 ? Ss 11:28 0:00 /root/.config/guix/current/bin/guix-daemon 12770
I ran strace on the first one.
Konrad.
[-- Attachment #2: guix-daemon-strace.log.gz --]
[-- Type: application/gzip, Size: 15404 bytes --]
next prev parent reply other threads:[~2018-09-11 9:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180717085541.g6nuycopf5kxoin7@thebird.nl>
[not found] ` <20180717191554.GA23234@jasmine.lan>
2018-07-17 22:28 ` bug#32183: New ‘guix pull’ /root/.config/current/bin/guix: Permission denied Ludovic Courtès
2018-07-23 22:28 ` Pjotr Prins
2018-07-26 13:50 ` Ludovic Courtès
2018-09-02 13:55 ` Ludovic Courtès
2018-09-02 14:28 ` Pjotr Prins
2018-09-02 20:04 ` Ludovic Courtès
2018-09-06 21:10 ` Pjotr Prins
2018-09-09 7:20 ` Pjotr Prins
2018-09-09 14:02 ` Pjotr Prins
2018-09-09 14:44 ` Ludovic Courtès
2018-09-11 9:34 ` Konrad Hinsen [this message]
2018-09-11 10:12 ` Ludovic Courtès
2018-09-11 13:23 ` Pjotr Prins
2018-09-11 13:58 ` Pjotr Prins
2018-09-11 14:27 ` Ludovic Courtès
2018-10-11 16:32 ` Ludovic Courtès
2018-10-12 6:59 ` Konrad Hinsen
2018-10-12 12:57 ` Ludovic Courtès
2018-10-15 11:59 ` Konrad Hinsen
2018-10-15 19:33 ` Ludovic Courtès
2018-10-16 10:41 ` Konrad Hinsen
2018-10-17 8:44 ` Ludovic Courtès
2018-10-17 9:17 ` Konrad Hinsen
2018-10-17 23:06 ` Ludovic Courtès
2018-11-02 14:38 ` swedebugia
2018-11-03 14:13 ` Ludovic Courtès
2018-10-14 18:12 ` Pjotr Prins
2018-09-11 14:26 ` Ludovic Courtès
2018-09-05 15:27 ` bug#32183: Me too! Konrad Hinsen
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=m1y3c89y3a.fsf@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=32183@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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).