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=EEe0Z2u45IuOaZiEqp16P6dSivpLYKLJRXzTnhzbejAgVWsrhnnPs
	htSH86CVLH3q10GANcHVnTrhnbT4OrswR9BNXYtkg7FKh+hK42DLYzZwVLk8q8IQ
	u7XESf6jtqhIQ6CeaPeQEWYzHPzAJ1tQ2wJpKzdZuRP4I4F+x8Tye0=
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=YWtLFwa2VZm21y0KBX9x0YishnI=; b=vSjHD+2uAlPbIINZPXYp1F67qc51
	t1U9JlJPUGJA7vpJLZEZJf6fKTlSePpY3BKNwcTcysf92/9/qCSjn9GYyi96qYyO
	hFfaC4MAJQuIaCUC3cAj0NQM0D+9lRauX0WbUaQXURd9EUCMoZ9NoopN27qPQXpB
	/8ev31iZ+pdiE/8=
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=1.3 required=5.0 tests=AWL,BAYES_40,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: U2FsdGVkX183E+ambKcu8DS5sCQBrSt9
Date: Fri, 26 Jul 2013 13:38:45 -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: <20130726173845.GA6578@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> <20130725181604 DOT GA2764 AT ednor DOT casa DOT cgf DOT cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130725181604.GA2764@ednor.casa.cgf.cx>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Thu, Jul 25, 2013 at 02:16:04PM -0400, Christopher Faylor wrote:
>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.

This is checked in.  The CYGWIN environment variable keyword is 'wincmdln'.

32 and 64 bit snapshots are uploaded.

http://cygwin.com/snapshots/

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