Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: 14 Sep 2001 12:13:16 -0400
Message-ID: <20010914161316.3768.qmail@lizard.curl.com>
From: Jonathan Kamens <jik AT curl DOT com>
To: jik AT curl DOT com
CC: cygwin-developers AT cygwin DOT com
In-reply-to: <20010914155645.3005.qmail@lizard.curl.com> (message from
	Jonathan Kamens on 14 Sep 2001 11:56:45 -0400)
Subject: Re: Successfully attached to hung "make -j2" process!
References:  <20010914155645 DOT 3005 DOT qmail AT lizard DOT curl DOT com>

I should probably have mentioned, in the description of the Make job
server, how it is that child Make processes have access to the job
server pipe, since that may be relevant.  If the job server is active,
all child Make processes get passed the command-line argument
"--jobserver-fds #,#" where "#,#" are the numbers of the file
descriptors at both ends of the pipe.  These file descriptors aren't
supposed to close on exec, so the child Make processes can access
them.

  jik