X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=jO84k7GlV5AlHdlOg6/suNsVQSL2P
	XDIy9zVSCub9e69DLOLIhmD2HI2iA+8BTFNi7zut7MJ5w97YEVgNFb2wE0EiSNnN
	RHlK1LJZ7lupFl1E3cfvu5WLg4V56FjK7CnI3taJRgKysMo5YvDyR0DcGpHnx8Un
	xPQcfM06uEgM34=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=KkxWFUeZ09D/7HVgZV3Uj0Xsq3Y=; b=UGm
	8hvr7SLznJ++IZafebJ/nfo8EsJ8L9cuJVPvuz8cc2YqbOkM1ZzNbK/MWxyHOQgh
	fHG3hyD7cKMne+pWZxCcHIq5SVnPYGcaP+idF5Km9EJOUVTJxIcBenkpTW8S9uRr
	oNUop7Cb8Jn6KyD/EaK0rKvjp3ky49n20f5vx/AA=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status: No, score=-3.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_MED,RCVD_IN_HOSTKARMA_W,RDNS_NONE,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1
X-IronPortListener: Outbound_SMTP
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFALPW8lGcKEeu/2dsb2JhbABbgwaBBb1egRkWdIIkAQEBAwESKEQLAgEIDRUUEB8TFwENAgQbGodoBp0wm1ePTDiDFm8DjjmPbIsGgxSCKg
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr AT ncbi DOT nlm DOT nih DOT gov>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: RE: inetd-like Windows processes with CYGWIN?
Date: Fri, 26 Jul 2013 20:07:34 +0000
Message-ID: <5F8AAC04F9616747BC4CC0E803D5907D0C3BF8F4@MLBXv04.nih.gov>
References: <5F8AAC04F9616747BC4CC0E803D5907D0C3BE8BE AT MLBXv04 DOT nih DOT gov>
In-Reply-To: <5F8AAC04F9616747BC4CC0E803D5907D0C3BE8BE@MLBXv04.nih.gov>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id r6QK7x63031043

> Also, I noticed that if I use the following command as "the native
> Windows process",
> 
> /cygdrive/c/Windows/system32/cmd.exe /C "COPY CON"
> 
> I see (the expected) pairs of CMD.EXE/conhost.exe in Windows Task Manager
> created per each request (none of CMD.EXEs are exiting as if waiting
> for the COPY commands to finish -- which is weird), but when the main
> CYGWIN process gets killed, it only clears up "CMD.EXE" leaving a bunch
> of "conhost.exe" behind, and they seem to hang around forever (manual
> cleanup is required).

Retracting this (partially):  there is no leaking of "conhost.exe",
only that "cmd.exe" waits for "copy" to finish (even though the requestor
may have been long gone).


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple