From: Mark H Weaver <mhw@netris.org>
To: swedebugia <swedebugia@riseup.net>
Cc: 34006@debbugs.gnu.org
Subject: bug#34006: Guix gc killed live roots - broke git
Date: Tue, 08 Jan 2019 02:50:53 -0500 [thread overview]
Message-ID: <87k1jfk2o7.fsf@netris.org> (raw)
In-Reply-To: <276035e4-7b63-31b7-9b83-e4311441dbe5@riseup.net> (swedebugia's message of "Mon, 7 Jan 2019 17:58:21 +0100")
Hi,
swedebugia <swedebugia@riseup.net> writes:
> On 2019-01-07 12:31, Ricardo Wurmus wrote:
>>
>>> $ git pull swedebugia
>>> fatal: unable to fork
>>>
>>> Stracing it reveals that it is missing something (see full attached):
>>
>> Where do you see that?
>
> Ah, sorry the full command was:
> strace git pull swedebugia
I looked at the strace output you provided, and didn't find any evidence
of a missing file, which I doubt would lead to the error message "unable
to fork" anyway. The short excerpt that you quoted in your earlier mail
showed the failure to find "/etc/ld.so.preload", but that's expected,
and does not indicate a problem. The problem might be happening in the
child process (/home/sdb/.guix-profile/libexec/git-core/git), so adding
the -f option to strace, i.e. "strace -f git pull swedebugia", might
yield more useful information.
If I'm not mistaken, "unable to fork" more likely indicates a lack of
available resources, possibly due to configured resource limits (see
ulimit(3) and the 'ulimit' bash builtin, e.g. try "ulimit -a").
Otherwise, I guess it could be due to restrictions imposed by the use of
a security framework.
Mark
next prev parent reply other threads:[~2019-01-08 7:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 10:07 bug#34006: Guix gc killed live roots - broke git swedebugia
2019-01-07 11:31 ` Ricardo Wurmus
2019-01-07 16:58 ` swedebugia
2019-01-07 17:52 ` Ricardo Wurmus
2019-01-08 7:50 ` Mark H Weaver [this message]
2019-01-08 8:50 ` swedebugia
2019-01-12 19:02 ` swedebugia
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=87k1jfk2o7.fsf@netris.org \
--to=mhw@netris.org \
--cc=34006@debbugs.gnu.org \
--cc=swedebugia@riseup.net \
/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.