Commit: efa5488448771f9cf6554b137d388ea5f3dc90c6
https://github.com/bagder/curl/commit/efa5488448771f9cf6554b137d388ea5f3dc90c6
Author: Marc Hoersken i...@marc-hoersken.de
Date: 2013-04-06 (Sat, 06 Apr 2013)
..
ftp.pm: Made Perl testsuite able to kill Windows processes
This patch
Hi Gisle,
2013/4/6 Gisle Vanem gva...@broadpark.no:
ftp.pm: Made Perl testsuite able to kill Windows processes
This patch uses a tool from Windows-XP Professional:
system(taskkill $filter nul 21);
I run Windows-XP Home and have no such tool. AFAICS,
one cannot get this from MS w/o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06.04.2013 14:49, Marc Hoersken wrote:
Hi Gisle,
2013/4/6 Gisle Vanem gva...@broadpark.no:
ftp.pm: Made Perl testsuite able to kill Windows processes
This patch uses a tool from Windows-XP Professional:
system(taskkill $filter nul 21);
Hi LRN,
2013/4/6 LRN lrn1...@gmail.com:
You can use Win32API Perl module and TerminateProcess or
SafeTerminateProcess.
Also, CreateJobObject + AssignProcessToJobObject can be used to
implement behaviour similar to kill -pid. Obviously, that also
requires Win32API module.
I added support for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06.04.2013 19:12, Marc Hoersken wrote:
Hi LRN,
2013/4/6 LRN lrn1...@gmail.com:
You can use Win32API Perl module and TerminateProcess or
SafeTerminateProcess. Also, CreateJobObject +
AssignProcessToJobObject can be used to implement
Hi LRN,
2013/4/6 LRN lrn1...@gmail.com:
The only advice i can give is to treat tskill failures gracefully. W32
is known to put processes into a state in which they still exist, but
cannot be interacted with, probably due to the fact that OS is
dismantling them at the moment. Killing such
