This is the mail archive of the
mailing list for the Cygwin project.
Re: SIGHUP on pty closure
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 12 Dec 2011 23:36:07 -0500
- Subject: Re: SIGHUP on pty closure
- References: <4E289D7B.firstname.lastname@example.org> <4E2D474A.email@example.com> <20110725151140.GA27310@ednor.casa.cgf.cx> <4E2D9FEA.firstname.lastname@example.org> <20110725170554.GB32493@ednor.casa.cgf.cx> <4E2DA77B.email@example.com>
- Reply-to: 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.
>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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple