Re: Bug report: Killing a native process may not actually kill it

On Thu, 29 Aug 2019, 02:38 Steven Penny, wrote: > On Wed, 28 Aug 2019 15:57:23, Quanah Gibson-Mount wrote: > > 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

Re: Bug report: Killing a native process may not actually kill it

On Wed, 28 Aug 2019 15:57:23, Quanah Gibson-Mount wrote: 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. I

Re: Bug report: Killing a native process may not actually kill it

--On Wednesday, August 28, 2019 2:33 PM -0700 Kaz Kylheku <920-082-4...@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

Re: Bug report: Killing a native process may not actually kill it

On 2019-08-28 08:59, Quanah Gibson-Mount wrote: --On Wednesday, August 28, 2019 6:45 PM +0200 Corinna Vinschen wrote: Not likely. Cygwin handles Ctrl-C by generating SIGINT. This only works reliably with Cygwin processes. There's $ /bin/kill -f to call the Win32 function

Re: Bug report: Killing a native process may not actually kill it

On Aug 28 08:59, Quanah Gibson-Mount wrote: > > > --On Wednesday, August 28, 2019 6:45 PM +0200 Corinna Vinschen > wrote: > > > Not likely. Cygwin handles Ctrl-C by generating SIGINT. This only > > works reliably with Cygwin processes. There's > > > > $ /bin/kill -f > > > > to call the

Re: Bug report: Killing a native process may not actually kill it

--On Wednesday, August 28, 2019 6:45 PM +0200 Corinna Vinschen wrote: Not likely. Cygwin handles Ctrl-C by generating SIGINT. This only works reliably with Cygwin processes. There's $ /bin/kill -f to call the Win32 function TerminateProcess(pid) on a non-Cygwin process or an

Re: Bug report: Killing a native process may not actually kill it

On Aug 28 08:18, Quanah Gibson-Mount wrote: > > > --On Thursday, July 25, 2019 11:32 AM -0700 Quanah Gibson-Mount > wrote: > > > As found and reported to the MSYS team back in 2006 by Howard Chu, if a > > native process is spawned, control-C, the kill command, etc, may not > > actually kill

Re: Bug report: Killing a native process may not actually kill it

--On Thursday, July 25, 2019 11:32 AM -0700 Quanah Gibson-Mount wrote: As found and reported to the MSYS team back in 2006 by Howard Chu, if a native process is spawned, control-C, the kill command, etc, may not actually kill the process. Details are here: I haven't seen a reply to

openldap on Cygwin (was: Bug report: Killing a native process may not actually kill it)

Quanah Gibson-Mount writes: […] Sorry for wedging in sideways, but I've looked into building a more up-to-date openldap and there's missing detection / configuration for Cygwin. Specifically, there's code trying to use robust POSIX mutexes, which Cygwin doesn't have. As there is no configure

Bug report: Killing a native process may not actually kill it

As found and reported to the MSYS team back in 2006 by Howard Chu, if a native process is spawned, control-C, the kill command, etc, may not actually kill the process. Details are here: as well as here: