X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-5.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<4FC4C7C6.6070603@cs.utoronto.ca>
References:	<4F3BEED9 DOT 8090909 AT w5pny DOT com> <4F3FEDC1 DOT 5010402 AT w5pny DOT com> <4FC3B6BD DOT 1010309 AT w5pny DOT com> <4FC4C7C6 DOT 6070603 AT cs DOT utoronto DOT ca>
Date:	Tue, 29 May 2012 19:27:52 +0100
Message-ID:	<CAHWeT-Z+G1p+1kqJCF5uO9pYrReKz9uFHq914ZSRmcTvdxLwmA@mail.gmail.com>
Subject:	Re: Mintty Log Off problem (now 1.7.16s)
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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id q4TISFMe012275

On 29 May 2012 13:57, Ryan Johnson wrote:
> On 28/05/2012 1:32 PM, Harry G McGavran Jr wrote:
>>
>>
>> On 02/18/12 11:28, Harry G McGavran Jr wrote:
>>>
>>> I've found a little more information -- this problem goes away
>>> if I change my default shell to dash.  Seems tcsh is involved somehow.
>>> It comes back when I change my default shell back to tcsh.
>>> Going back to tcsh 6.18.00-2 does not help.
>>>
>>> Given the deathly silence to my request below, I must be the only
>>> one experiencing this, but it happens on both of my machines.
>>>
>>>     Harry
>>>
>>> On 02/15/12 10:43, Harry G McGavran Jr wrote:
>>>>
>>>> With Cygwin 1.7.10(0.259/5/3) upon logging off Windows XP SP3
>>>> I get a pop-up window "End Program - C:\cygwin\bin\mintty.exe"
>>>> with a "End Now" and "Cancel" button every time I log off
>>>> Windows and I have somewhere in that Windows session run
>>>> the Mintty shortcut which has "C:\cygwin\bin\mintty -u -"
>>>> in it and my default shell is tcsh. This never happened
>>>> with previous Cygwin releases. What's even more interesting
>>>> is that in all cases I exit all my programs before logging
>>>> off, including the mintty window. I've even tried hitting
>>>> the "Cancel" button and then looking for a process named
>>>> mintty or "Terminal" (since that's what mintty's description
>>>> is and that is used by some process tools) with both Process Explorer
>>>> and Task Manager, but I can find no such process -- and then
>>>> when I try to log off again not having found such a process
>>>> the pop-up comes back and I can't log off until I hit
>>>> "End Now".
>>>>
>>>> Since I haven't seen any reports of this on this list, I must
>>>> be about the only one this is happening to. Any clues as to
>>>> what I can do to find out what Windows is actually failing to stop
>>>> when I try to log off having run mintty beforehand?
>>
>> I'm puzzled why others aren't seeing this or aren't reporting it,
>> but this problem seems to be back with 1.7.15 and I've now tried
>> the latest snapshot (May 25) and it's back there too. It occurred
>> with 1.7.10 and then got fixed, but now it seems to be back.
>
> I routinely encounter mintty windows that don't close after I exit the login
> shell they run (even though they contain no visible child processes), but
> they can still be closed using the big red "X" in the corner...

Mintty closes when it gets an EOF from the underlying pseudo terminal
device. This happens when there are no more processes connected to it.
The Cygwin console behaves similarly, but other terminal emulators do
not: they close once the direct child process exits no matter whether
other processes are still connected.

Backgrounding a process with '&' or nohupping it doesn't break that
connection, but invoking it through the 'setsid' utility from the
util-linux package does.

See also http://code.google.com/p/mintty/issues/detail?id=319.

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 -