Git Bash 错误:无法分叉子进程:权限被拒绝 (-1) [英] Git Bash Error: Could not fork child process: Permission denied (-1)

问题描述

我使用 choco install git 由 Chocolatey 安装了适用于 Windows 的 Git.它已在许多卫星上完美运行.

几天前，当我打开 Git Bash 时，出现的窗口如下:

标题栏:/usr/bin/bash --login -i

窗口内容:错误:无法分叉子进程:权限被拒绝(-1)

我的同事也在他的机器上收到相同的错误消息.我们正在使用加入 Windows 域的企业公司笔记本电脑.支持这些笔记本电脑的 IT 团队对 Git 了解不多，因为大多数组织都在使用 TFS，因此他们不确定如何支持这一点.是否可能是组策略更新或类似情况导致了这种情况?该组织也正在转向 SSO(我认为是通过 Azure AD) - 这可能相关吗?

我尝试了以下方法:

• 将 git 更新到最新的 v2.16.1.2
• 这个答案:

  解决方案

  我找到了解决方案.

  就我而言，问题是由 McAfee Endpoint Security 中的新政策引起的.

  为了解决这个问题，我的 IT 支持管理员为 Git 可执行文件创建了一个新的允许策略.我使用 McAfee Agent 状态监视器中的检查/执行策略更新了 McAfee.之后，由于一些只读权限问题，我不得不重新安装 Git.问题解决了.其他组织的解决方案可能有所不同，但重点是，如果您在企业网络中突然遇到此问题，请首先查看您的端点安全解决方案策略，将其作为最可能的问题原因.

  I have Git for Windows installed by Chocolatey using choco install git. It has been working perfectly for many moons.

  A couple of days ago when I opened Git Bash, the window appears with the following:

  Title Bar: /usr/bin/bash --login -i

  Window content: Error: Could not fork child process: Permission denied (-1)

  My colleague is also receiving the same error message on his machine. We are using enterprise company laptops joined to a Windows domain. The IT team who support these laptops don't know a lot about Git as most of the organisation is using TFS, so they are not sure how to support this. Is it likely a Group Policy update or similar might have caused this? The organisation is also moving towards SSO (I think through Azure AD) - could this be related?

  I have tried the following:

  • Update git to the latest v2.16.1.2
  • This answer: https://stackoverflow.com/a/45803951/335366
  • Reboot windows
  • Run Git Bash as Administrator
  • Run Git Bash using the Explorer Context menu: "Git Bash Here"

  Nothing works. How can I resolve this either locally or through the domain / active directory / group policy?

  Git GUI seems to work on my colleague's machine but is not working on mine. When I load Git GUI I get error:

  解决方案

  I found the solution to this.

  In my case, the issue was being caused by a new policy in McAfee Endpoint Security.

  To resolve, my IT Support admin created a new Allow policy for the Git executables. I updated McAfee with Check/Enforce policies in the McAfee Agent Status Monitor. Following that, I had to reinstall Git due to some read-only permission issue. Problem solved. The solution may differ for other organisations but the main point is that if you encounter this issue suddenly in an Enterprise network, look to your endpoint security solution policies first as the most probable cause of the issue.

  这篇关于Git Bash 错误:无法分叉子进程:权限被拒绝 (-1)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！