X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,TW_CG
X-Spam-Check-By:	sourceware.org
X-Mail-Handler:	MailHop Outbound by DynDNS
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX19j7ja3++z4twqW0AzaMJ5h
Date:	Mon, 12 Dec 2011 23:36:07 -0500
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: SIGHUP on pty closure
Message-ID:	<20111213043607.GA5329@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4E289D7B DOT 4050103 AT gmail DOT com> <4E2D474A DOT 4000509 AT gmail DOT com> <20110725151140 DOT GA27310 AT ednor DOT casa DOT cgf DOT cx> <4E2D9FEA DOT 1020900 AT gmail DOT com> <20110725170554 DOT GB32493 AT ednor DOT casa DOT cgf DOT cx> <4E2DA77B DOT 2030909 AT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<4E2DA77B.2030909@gmail.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)
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 Mon, Jul 25, 2011 at 07:27:23PM +0200, Marco Atzeri wrote:
>On 25/07/2011 19.05, Christopher Faylor wrote:
>
>>
>> "sleeping and waiting for signal" would mean that "bash is not waiting
>> for input".  If bash isn't waiting for input that would explain the
>> problem.  However, I would expect that bash, in this scenario, to be
>> waiting for input.  I was hoping you'd provide insight into whether that
>> was the case or not.
>>
>> cgf
>
>Sorry, I will try to be more clear, for what I understood of mc.
>
>With CTRL-O the foreground is switched between mc and bash
>(or viceversa) , so when mc is on foreground bash is not
>waiting for input, but for a signal to wake up again.
>
>Mc exits following F10 key press and bash should follow
>when it receives SIGHUP.

I tracked down a place where SIGHUP was not getting sent correctly
so I may have fixed this in recent snapshots.  No guarantees though.

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

- Raw text -