DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=TwSWz+DB0Pd9bODQ
	wE0RBqUEd5nqyyunQCmnZvMAnxKK13bh0mVh2uSBby1xtgMvanXTUrWvJQVGgkxa
	zWGmP59UPSeVt9D/KbRx8o3BEMRAnLZwo4qm7bonErD+ok+g6YQNr/KRo9ptKzgw
	Jx+7UxHATXOyWPgSa4XpzmWs8vk=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Cygwin windows won't close
To: cygwin@cygwin.com
References: <CY4PR06MB288686C9ED2BE9D835EC6309BEE40@CY4PR06MB2886.namprd06.prod.outlook.com> <244059378.20181007032751@yandex.ru> <CY4PR06MB2886ED3C2C865CB75640EC48BEE60@CY4PR06MB2886.namprd06.prod.outlook.com> <1829128594.20181008205201@yandex.ru> <CY4PR06MB2886C8BCC03A804749BFB2F6BEE60@CY4PR06MB2886.namprd06.prod.outlook.com> <1485439048.20181009144650@yandex.ru> <CY4PR06MB28868B3F57650CD36FD1D97ABEE70@CY4PR06MB2886.namprd06.prod.outlook.com> <a8097f95-0221-b726-6631-0cde2e0b02d1@gmail.com> <fcd703b4-bccd-4a97-a953-8aec9279fed8@towo.net>
From: Thomas Wolff <towo@towo.net>
Message-ID: <dc1aead1-404e-fee7-068b-88a4aaa63959@towo.net>
Date: Sun, 14 Oct 2018 06:36:57 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <fcd703b4-bccd-4a97-a953-8aec9279fed8@towo.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


Am 10.10.2018 um 08:37 schrieb Thomas Wolff:
>
> Am 09.10.2018 um 20:46 schrieb Marco Atzeri:
>> Am 09.10.2018 um 19:22 schrieb Ziegelmiller, Lyle(AWF) via cygwin:
>>> Then I don't see much of the cause for such a behavior from Cygwin 
>>> side.
>>> May be other software interfering. Do you have a particularly 
>>> zealous "antivirus", pehaps?
>>>
>>> We're using "Symantec Endpoint Protection", Version 14.
>>>
>>> I could see an anti-virus program preventing the execution of a 
>>> Cygwin window, but not the closing of one.
>>>
>>
>> I have seen Symantec in the past creating such problems.
>> Probably they inject something in the call sequence.
> Which brings me to this suggestions: Please try option 
> ConfirmExit=false, does the behaviour change?
> Thomas
Despite pending response to my diagnostic request, it can well be that 
the start of `ps` to construct the process list shown with the exit 
confirmation has this effect. I've uploaded a patch to avoid it, 
constructing the list internally from /proc, to the mintty repository.
Thomas

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