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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=XkJBX6eqWxV0lsJJ+1jDj8JZE2Dq6WxYk/aUlXS6YoCwlfreYLqSF
	IaAWGEyqj7ZscFsIh2TquAOcUBTDWkRpEN+dy5nB08i3xYR49eP0oZf0Pe7K3nTm
	9b+izDeIwICHO4XSdh5LApSGvQ3XIzlHyUVDUZos9GEJ/R2KoYbH4U=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=db7H/6UCxmuuis8+Q2PM6imTE30=; b=pq9GYkogNPugwauOC8GSP6SZ7TjQ
	jv0+EwvfgH6jJXfCyNumHOws775/y4JgwAZSzfMxoFg0bs9knsdYYk6bvfYPlsKU
	8GSems9rhM9iUrvwZCTtXJlQyDekkeRZ2BvcPJ9YXF15f2jjKPLeu7Mz4Emkrdgu
	oIVdVLQWkADh6/c=
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=0.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RDNS_NONE autolearn=no version=3.3.1
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX18f0yyCyOGHHO7qzxtQHZ+Q
Date:	Thu, 25 Jul 2013 14:16:04 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
Subject:	Re: Process command lines for Cygwin processes no longer viewable in Windows task manager as of Cygwin 1.7.21
Message-ID:	<20130725181604.GA2764@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
References:	<51F08F9D DOT 6020606 AT coverity DOT com> <20130725082814 DOT GA5124 AT calimero DOT vinschen DOT de> <51F1265B DOT 1040704 AT cwilson DOT fastmail DOT fm>
MIME-Version:	1.0
In-Reply-To:	<51F1265B.1040704@cwilson.fastmail.fm>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Thu, Jul 25, 2013 at 09:21:31AM -0400, Charles Wilson wrote:
>On 7/25/2013 4:28 AM, Corinna Vinschen wrote:
>> On Jul 24 22:38, Tom Honermann wrote:
>>> My suspicion that this started with 1.7.21 is based on Corinna's
>>> comments in http://cygwin.com/ml/cygwin/2013-07/msg00343.html and
>>> other anecdotal evidence of new problems occurring as of that
>>> release.
>>
>> This is by design now as described in the aforementioned posting.  If
>> you want to see the command line of a Cygwin application called by
>> another Cygwin application, see /proc/$pid/cmdline.
>
>Would a patch to restore the previous operation based on a $CYGWIN 
>variable setting be acceptable?

I actually had the same thought and have a patch waiting for Corinna's
comment sitting in my sandbox.

cgf

--
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

- Raw text -