X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 From: Sravan Bhamidipati Date: Thu, 19 May 2011 10:28:53 +0530 Message-ID: Subject: Process Execution from Cygwin Shells To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Steps to reproduce: 1. Open "Process Monitor" and filter for events of type "Operation" and value "Process Create". 2. Open a Cygwin shell (using cygwin.bat or mintty or rxvt): bash or ksh, e.g. 3. Type any command that is not a shell built-in, say "clear" or "cmd". 4. Notice that "Process Monitor" captured two process creation events related to the invoked command: a new child shell and another of the invoked command. 5. Open the command prompt, cd to $CYGWIN\bin, and type the same command (a Cygwin command that can be executed directly from cmd will also do). 6. Notice that "Process Monitor" captured only one process creation event: of the invoked command. This seems very strange to me. The behavior applies even when executing a Shell script. I noticed identical behavior when using MinGW Shell as well. Shells in Unix-based OSs don't behave this way. Why is this happening? Can something be done about it? Regards, Sravan -- 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