summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlexey Sokolov <sokolov@google.com>2016-03-04 19:42:15 +0000
committerCorinna Vinschen <corinna@vinschen.de>2016-03-04 22:02:35 +0100
commitbf45e12fb627ecc46f4758dbb1baddff775d4381 (patch)
tree9daa57f8bec60c1a26e66ee58feea1ef6b27b66a
parent2cd76694e1d7021759cca8f940092186530dfdae (diff)
downloadcygnal-bf45e12fb627ecc46f4758dbb1baddff775d4381.tar.gz
cygnal-bf45e12fb627ecc46f4758dbb1baddff775d4381.tar.bz2
cygnal-bf45e12fb627ecc46f4758dbb1baddff775d4381.zip
Mention 64-bit Cygwin as another remedy for fork() failures.
-rw-r--r--winsup/doc/faq-using.xml4
1 files changed, 3 insertions, 1 deletions
diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml
index ae72145ab..f6d4b8e6a 100644
--- a/winsup/doc/faq-using.xml
+++ b/winsup/doc/faq-using.xml
@@ -1394,13 +1394,15 @@ such as virtual memory paging and file caching.</para>
<para><itemizedlist>
<listitem>Restart whatever process is trying (and failing) to use
<literal>fork()</literal>. Sometimes Windows sets up a process
- environment that is even more hostile to fork() than usual.</listitem>
+ environment that is even more hostile to <literal>fork()</literal> than usual.</listitem>
<listitem>Ensure that you have eliminated (not just disabled) all
software on the <xref linkend="faq.using.bloda"/>.
</listitem>
<listitem>Read the 'rebase' package README in
<literal>/usr/share/doc/rebase/</literal>, and follow the
instructions there to run 'rebaseall'.</listitem>
+ <listitem>Switch from 32-bit Cygwin to 64-bit Cygwin, if your OS and CPU support that.
+ With the bigger address space <literal>fork()</literal> is less likely to fail.</listitem>
</itemizedlist></para>
<para>Please note that installing new packages or updating existing
ones undoes the effects of rebaseall and often causes fork() failures