X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 4 Jan 2010 18:47:29 -0500 From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com> To: cygwin AT cygwin DOT com Subject: Re: procps returns parent's cmdline for a child process in cygwin 1.7.1 Message-ID: <20100104234729.GA12923@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <5b0039af1001041238y25c0eaa2g1fbe135fdfe62a60 AT mail DOT gmail DOT com> <5b0039af1001041410r28fcc185s7ab8ff45f988cfbc AT mail DOT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5b0039af1001041410r28fcc185s7ab8ff45f988cfbc@mail.gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: <cygwin.cygwin.com> List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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 On Mon, Jan 04, 2010 at 02:10:19PM -0800, Jonathan Schedler wrote: >The following foo.sh script reproduces what I am seeing, using >notepad.exe instead of java.exe > >#!/bin/bash > >notepad & > >procps -eF > >If the above is in a file named foo.sh, the output of procps -eF will be > >Jon 5072 4756 0 1390 7548 0 14:08 tty0 00:00:00 >/usr/bin/bash ./foo.sh >Jon 6012 5072 0 407 8576 0 14:08 tty0 00:00:00 >/usr/bin/bash ./foo.sh >Jon 5716 5072 0 1185 6012 0 14:08 tty0 00:00:00 procps -eF > >Notice the procps command shows up correctly. So it seems I have an >issue displaying normal windows exe's in procps output. AFAIK, Cygwin has always worked like this. I just tried it with Cygwin 1.5 and see the same behavior and, it's what I'd expect since retrieving the command line output requires a cooperative cygwin process. 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