From: Quanah Gibson-Mount <quanah@symas.com>
To: Kaz Kylheku <920-082-4242@kylheku.com>, cygwin@cygwin.com
Subject: Re: Bug report: Killing a native process may not actually kill it
Date: Thu, 29 Aug 2019 00:02:00 -0000 [thread overview]
Message-ID: <BABD7A9897B18A11C35CDBBE@[192.168.1.144]> (raw)
In-Reply-To: <893c47a5235335c035a83536ab3cd899@mail.kylheku.com>
--On Wednesday, August 28, 2019 2:33 PM -0700 Kaz Kylheku
<920-082-4242@kylheku.com> wrote:
> Cygwin can't introduce Unix-like shutdown mechanisms (like the
> handling a non-fatal signal) into non-Cygwin processes which have
> no concept of that. It makes no sense.
My original post contained a link to a patch allowing for Cygwin to
correctly terminate native Windows processes. I understand it is not the
position of the Cygwin project to deal with situation, so I think we can
just let it drop.
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--
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
next prev parent reply other threads:[~2019-08-28 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 17:32 Quanah Gibson-Mount
2019-07-25 18:30 ` openldap on Cygwin (was: Bug report: Killing a native process may not actually kill it) Achim Gratz
2019-07-25 19:04 ` openldap on Cygwin Quanah Gibson-Mount
2019-08-28 15:46 ` Bug report: Killing a native process may not actually kill it Quanah Gibson-Mount
2019-08-28 15:59 ` Corinna Vinschen
2019-08-28 16:02 ` Quanah Gibson-Mount
2019-08-28 20:33 ` Corinna Vinschen
2019-08-28 22:43 ` Kaz Kylheku
2019-08-29 0:02 ` Quanah Gibson-Mount [this message]
2019-08-29 1:01 ` Steven Penny
2019-09-03 5:38 ` Ray Donnelly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BABD7A9897B18A11C35CDBBE@[192.168.1.144]' \
--to=quanah@symas.com \
--cc=920-082-4242@kylheku.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).