This is the mail archive of the
cygwin-patches
mailing list for the Cygwin project.
Re: Extend faq.using to discuss fork failures
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin-patches at cygwin dot com
- Date: Thu, 3 Nov 2011 17:05:19 -0400
- Subject: Re: Extend faq.using to discuss fork failures
- References: <4E570031.4080800@cs.utoronto.ca> <20110830090020.GE30452@calimero.vinschen.de> <4E5CE899.4030605@cs.utoronto.ca> <4EB2C2CD.1080400@dronecode.org.uk>
- Reply-to: cygwin-patches at cygwin dot com
On Thu, Nov 03, 2011 at 04:35:25PM +0000, Jon TURNEY wrote:
>On 30/08/2011 14:41, Ryan Johnson wrote:
>> That sounds reasonable, though I suspect we'd want want to keep the concluding
>> bits in the FAQ as well. Unfortunately, summertime free time has come to an
>> end so I don't know when I'll get to this next. Perhaps a good compromise for
>> now would be for you to post only the first FAQ question? That would at least
>> cut traffic to the cygwin ML a bit.
>
>I've updated Ryan's patch to hopefully address the comments made, polished the
>language a bit in places, and split it into a patch for the FAQ which just
>says how to fix problems and a patch for the UG which contains the technical
>details.
>Index: doc/faq-using.xml
>===================================================================
>RCS file: /cvs/src/src/winsup/doc/faq-using.xml,v
>retrieving revision 1.35
>diff -u -p -r1.35 faq-using.xml
>--- doc/faq-using.xml 4 Aug 2011 18:25:41 -0000 1.35
>+++ doc/faq-using.xml 3 Nov 2011 16:26:56 -0000
>@@ -1099,7 +1099,7 @@ it.</para>
> IPv6 stack, see the <ulink url="http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx">Microsoft TechNet IPv6 FAQ article</ulink>
> </para></answer></qandaentry>
>
>-<qandaentry id="faq.using.bloda">
>+<qandaentry id="faq.using.bloda" xreflabel="BLODA">
> <question><para>What applications have been found to interfere with Cygwin?</para></question>
> <answer>
>
>@@ -1199,3 +1199,38 @@ such as virtual memory paging and file c
> </listitem>
> </itemizedlist></para>
> </answer></qandaentry>
>+
>+<qandaentry id='faq.using.fixing-fork-failures'>
>+ <question><para>How do I fix <literal>fork()</literal> failures?</para></question>
>+ <answer>
>+ <para>Unfortunately, Windows can be quite hostile to a
I would still prefer eschewing actively negative words like "hostile" and just
neutrally stating that Windows does not use a fork/exec model and does not offer
any easy way to implement fork.
I'd also like to see specific errors mentioned so that when people are searching for
a solution to the problem they will be able to find it in the FAQ.
cgf