X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.4 required=5.0 tests=AWL,BAYES_50,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<iarbc4$lcp$1@dough.gmane.org>
References:	<iar8kd$8u7$1 AT dough DOT gmane DOT org> <250110 DOT 4409 DOT qm AT web25507 DOT mail DOT ukl DOT yahoo DOT com> <iarbc4$lcp$1 AT dough DOT gmane DOT org>
Date:	Wed, 3 Nov 2010 19:48:22 +0000
Message-ID:	<AANLkTikJLU-kbNRj7oakk_eYiatOH3XYDC3wuQWDAwOD@mail.gmail.com>
Subject:	Re: R: Why mc start without subshell by default?
From:	Andy Koppe <andy DOT koppe AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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 3 November 2010 09:52, Oleksandr Gavenko wrote:
> On 03.11.2010 11:14, Marco Atzeri wrote:
>>
>> --- Mer 3/11/10, Oleksandr Gavenko =C2=A0ha scritto:
>>
>>> I can turn on subshell by:
>>>
>>> =C2=A0 $ mc -U
>>>
>>> This is useful by default or I miss something?
>>>
>>>
>>
>> It is useful but there is one problem on cygwin.
>> When you close mc the subshell will not exit, so you will finish
>> with a "zombie" bash shell running.
>>
> Oh! I recall that I already wrote about this:
>
> C-o in GNU MC and mintty/rxvt issue?
> http://thread.gmane.org/gmane.os.cygwin/118690/focus=3D118693
>
> mc --subshell after exit forget kill bash.
> http://thread.gmane.org/gmane.os.cygwin/118702

A related issue is that when you close any of the pty-based terminals
with mc started from bash running in it, the mc process doesn't get
killed. Bash does of course forward the SIGHUP it gets from the
terminal to its child processes, and manually sending SIGHUP to the
orphaned mc does get rid of it.

A similar issue was previously reported against the joe and mined
editors at http://cygwin.com/ml/cygwin/2010-04/msg01013.html. This
still needs a simple test case though.

Andy

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

- Raw text -