busybox-w32, branch dscho-kill-gently

timeout: use new kill(2) to signal child

2017-09-26T15:40:37+00:00

win32: silence warning about unused parameter

2017-09-26T09:44:17+00:00

win32: allow kill to send signal number 0

2017-09-26T08:38:47+00:00

According to the man page: If sig is 0, then no signal is sent, but existence and permission checks are still performed

win32: improvements to implementation of kill(2)

2017-08-27T07:47:20+00:00

Extend the implementation of kill(2) so that: - Sending the TERM signal asks the target process to exit. As on Unix it may not comply. - Sending the KILL signal forcibly terminates the target process. - Using a negative pid treats the target process as a process group leader and signals it and all of its descendants. - Using a pid of zero treats the current process as a process group leader and signals it and all of its descendants. Signed-off-by: Ron Yorston

kill: use gentler method than TerminateProcess()

2017-08-25T21:11:19+00:00

As Git for Windows' source code recently learned, let's also avoid using TerminateProcess() in BusyBox-w32: it does not allow the killed processes' atexit() handlers to run. Instead, jump through a couple of hoops by injecting a remote thread that executes the ExitProcess() function. This allows the atexit() handlers to run, at which point the exit code of the process can already be queried via GetExitCodeProcess(), and appropriate action can be taken, such as killing child processes. Signed-off-by: Johannes Schindelin

libbb: don't compile various Linux-specific functions

2017-08-24T12:47:41+00:00

xfuncs_printf.c includes a number of Linux-specific functions. They handle things like SELinux, ioctls, devices and forking. Nothing in busybox-w32 uses them, so don't compile them.

cpio: disable pass-through mode (-p) in default configuration

2017-08-24T12:46:10+00:00

Pass-through mode never worked: it uses fork().

mode_string: S_IFBLK differs between Windows and Unix

2017-08-24T08:12:18+00:00

It is a bit wrong to make that much of a hard-coded assumption, anyway. Maybe a better way would be to test whether the S_IF* constants are in a specific range. But then, it is probably not worth the time to investigate that. Signed-off-by: Johannes Schindelin Signed-off-by: Ron Yorston

xconnect: avoid using getsockname/getpeername on Windows

2017-08-24T08:12:18+00:00

The semantics of said functions is a bit different on Windows than on Linux: it takes a `SOCKET` parameter instead of an `int` parameter, as Windows does not use file descriptors for sockets. The callers of these functions are only used in the daemons anyway, though, and those are not compiled in busybox-w32. Therefore, let's simply skip compiling those functions on Windows (as well as `get_lsa()`, which would now be unused otherwise). Signed-off-by: Johannes Schindelin Signed-off-by: Ron Yorston

mingw: accommodate for BusyBox' assumptions about isatty()

2017-08-24T08:12:10+00:00

On Windows, isatty(fd) determines whether the file descriptor refers to a character device. The thing is: even NUL or a printer is a character device. BusyBox thinks, however, that isatty() only returns non-zero for an interactive terminal. So let's shadow isatty() by a version that answers the question BusyBox wants to have answered. Signed-off-by: Johannes Schindelin Signed-off-by: Ron Yorston