From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "M. Abuhena Sobuj" <abuhenasobuj@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Error: could not fork child process: Resource temporarily unavailable (-1)
Date: Mon, 2 Jan 2017 11:58:18 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1701021155350.3469@virtualbox> (raw)
In-Reply-To: <CACkJq_gQQURdyUf5HvSqvw0Ee_yjCnFZ0DXJxZt42JOwEOd2tg@mail.gmail.com>
Hi,
On Mon, 2 Jan 2017, M. Abuhena Sobuj wrote:
> My Git Bash was perfect but suddenly It stooped work for me.
>
> I just got message
> "Error: could not fork child process: Resource temporarily unavailable (-1).
> DLL rebasing may be required. See 'rebaseall / rebase --help'."
Is this a 32-bit system? If so, simply try to reinstall Git for Windows,
that should make it work again [*1*].
If that does not solve the problem, you will want to open a ticket at
https://github.com/git-for-windows/git/issues/new
Ciao,
Johannes
Footnote *1*: https://github.com/git-for-windows/git/wiki/32-bit-issues
prev parent reply other threads:[~2017-01-02 10:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 10:36 Error: could not fork child process: Resource temporarily unavailable (-1) M. Abuhena Sobuj
2017-01-02 10:58 ` Johannes Schindelin [this message]
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=alpine.DEB.2.20.1701021155350.3469@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=abuhenasobuj@gmail.com \
--cc=git@vger.kernel.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