* [PATCH] Mention 64-bit Cygwin as another remedy for fork() failures.
@ 2016-03-04 19:57 Alexey Sokolov
2016-03-04 21:04 ` Corinna Vinschen
0 siblings, 1 reply; 2+ messages in thread
From: Alexey Sokolov @ 2016-03-04 19:57 UTC (permalink / raw)
To: cygwin-patches
[-- Attachment #1: Type: text/plain, Size: 118 bytes --]
Hello, patch to FAQ is attached.
--
Alexey Sokolov | SRE, Software Engineer | sokolov@google.com | +353 87 3767 850
[-- Attachment #2: 0001-Mention-64-bit-Cygwin-as-another-remedy-for-fork-fai.patch --]
[-- Type: application/octet-stream, Size: 1571 bytes --]
From 4070acc574dce41f6a98848a66626b26be4cdf8c Mon Sep 17 00:00:00 2001
From: Alexey Sokolov <sokolov@google.com>
Date: Fri, 4 Mar 2016 19:42:15 +0000
Subject: [PATCH] Mention 64-bit Cygwin as another remedy for fork() failures.
---
winsup/doc/faq-using.xml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml
index ae72145..f6d4b8e 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
--
2.6.2
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] Mention 64-bit Cygwin as another remedy for fork() failures.
2016-03-04 19:57 [PATCH] Mention 64-bit Cygwin as another remedy for fork() failures Alexey Sokolov
@ 2016-03-04 21:04 ` Corinna Vinschen
0 siblings, 0 replies; 2+ messages in thread
From: Corinna Vinschen @ 2016-03-04 21:04 UTC (permalink / raw)
To: cygwin-patches
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
On Mar 4 19:56, Alexey Sokolov wrote:
> Hello, patch to FAQ is attached.
Applied.
Thanks you,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-03-04 21:04 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-03-04 19:57 [PATCH] Mention 64-bit Cygwin as another remedy for fork() failures Alexey Sokolov
2016-03-04 21:04 ` Corinna Vinschen
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).