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=jOOTNSdduGyUQQjvRZNeYPGtfk/k1VjoPnBsR+NmNrqvC4w8P+F54
	mP5f8PQ91PQjF8QQobFJLwIXNLEWemRu1bBa2XR+pokQGv2r5Anspv5uHflB3bWx
	xGkIvLrFRop2dYoQNhxBdZVZnCm9Cd7JckrCZpdked/ZN9qdgLQ8FU=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Tue, 30 Jul 2013 13:54:33 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Process command lines for Cygwin processes no longer viewable in Windows task manager as of Cygwin 1.7.21
Message-ID: <20130730175433.GA3285@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <51F08F9D.6020606@coverity.com> <20130725082814.GA5124@calimero.vinschen.de> <51F1265B.1040704@cwilson.fastmail.fm> <20130725181604.GA2764@ednor.casa.cgf.cx> <20130726173845.GA6578@ednor.casa.cgf.cx> <51F2B8C5.6020402@coverity.com> <51F7FD45.4050508@coverity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51F7FD45.4050508@coverity.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Tue, Jul 30, 2013 at 01:52:05PM -0400, Tom Honermann wrote:
>On 07/26/2013 01:58 PM, Tom Honermann wrote:
>> On 07/26/2013 01:38 PM, Christopher Faylor wrote:
>>> 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'.
>>
>> Thank you, that is much appreciated.
>>
>>> 32 and 64 bit snapshots are uploaded.
>>>
>>> http://cygwin.com/snapshots/
>>
>> I'll test (probably 32-bit only) and report if any problems appear.
>
>Tests passed, changes look good, thanks again.
>
>The upgrade guide [1] doesn't list the new keyword.  Should I expect it 
>to be updated when 1.7.23 is released?
>
>[1]: http://cygwin.com/cygwin-ug-net/using-cygwinenv.html

Obviously we're not going to update the web page with a feature that
doesn't work in the current release.

http://cygwin.com/ml/cygwin-cvs/2013-q3/msg00039.html

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