X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=2.3 required=5.0	tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,KHOP_THREADED,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Date: Sat, 5 May 2012 15:31:06 +0400
From: Andrey Repin <anrdaemon AT freemail DOT ru>
Reply-To: Andrey Repin <cygwin AT cygwin DOT com>
Message-ID: <759745567.20120505153106@mtu-net.ru>
To: Petrisor Eddy-Marian-B36037 <B36037 AT freescale DOT com>, cygwin AT cygwin DOT com
Subject: Re: 'cmd /C start cmd' no longer non-blocking (base-cygwin 3.1-1), but used to work (in base-cygwin 3.0-1)
In-Reply-To: <4C337258C4FF8145842DBA13279005D882F882@039-SN1MPN1-001.039d.mgd.msft.net>
References: <4C337258C4FF8145842DBA13279005D882F882 AT 039-SN1MPN1-001 DOT 039d DOT mgd DOT msft DOT net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
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

Greetings, Petrisor Eddy-Marian-B36037!

> I am using at work cygwin on various machines (XP and Windows 7) and made
> several scripts that use gnu utilities from cygwin. One of those is a script
> that starts in paralel instances of cmd various parts of a build system
> through a sh script that invokes 'cmd /C start ...'

Why? Aren't your default ComSpec isn't CMD already?

> to start those parts of the build system in a non-blocking fashion.

If it's (b?a|tc)?sh script - use backgrounding (The &)
If it's a CMD script - use backgrounding (START "" /B "command" args)
Problem solved.

> Recently, on one of the machines which had its cygwin installation upgraded,
> I have observed that the cmd instances do not start in a non-blocking
> fashion anymore, but instead wait for the process to finish.


> To be more precise, following the following steps should lead to two
> interactive windows, one with the sh prompt and one with the cmd prompt,
> both waiting for user input:
> 1 - start a cygwin (or sh) command window
> 2 - type "cmd /C start cmd"

> Expected result:
> Two interactive and usable windows, one with the sh prompt, one with the cmd
> prompt, both waiting for user input.

For new interactive windows from withing Cygwin shell - use run program. And
again, backgrounding, if necessary.

> Actual result:
> Two windows, one with sh and one with cmd, Cygwin/sh window blocked and waiting for the cmd window to finish.


--
WBR,
Andrey Repin (anrdaemon AT freemail DOT ru) 05.05.2012, <15:27>

Sorry for my terrible english...


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