Guido U. Draheim
Guido U. Draheim
Here's seperate testprogram [os_waitpid_broken.py](https://github.com/gdraheim/docker-systemctl-replacement/files/2370730/os_waitpid_broken.py.txt) RESULTS: > python os_waitpid_broken.py -c "/bin/false" === RESULTS ['/bin/false'] FROM centos:7.4.1708 => 1 FROM ubuntu:18.04 => 1 FROM ubuntu:16.04 => 1 FROM opensuse/leap:15.0 => 1 >...
The unix standard is a bit ambigous here http://pubs.opengroup.org/onlinepubs/009696899/utilities/kill.html > EXITSTATUS = 0 > At least one matching process was found for each pid operand, and the specified signal was...
Actually, gnu coreutils do have a testcase for it. http://git.savannah.gnu.org/cgit/coreutils.git/tree/tests/misc/kill.sh # params required returns_ 1 env kill || fail=1 returns_ 1 env kill -TERM || fail=1
and there is difference for that test as well > python os_waitpid_broken.py -c "/bin/kill -TERM" --direct === RESULTS ['/bin/kill', '-TERM'] FROM centos:7.4.1708 => 1 FROM ubuntu:18.04 => 1 FROM ubuntu:16.04...
There is a hint in the ubuntu coreutils bug tracker that /bin/kill does not come from "gnu coreutils" but from the "procps" package. https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/141168 However that does not seem to...
checking on all available ubuntu docker images: python os_waitpid_broken.py -c "/bin/kill -TERM" --direct ubuntu:14.04 ubuntu:16.04 ubuntu:18.04 ubuntu:18.10 === RESULTS ['/bin/kill', '-TERM'] FROM ubuntu:14.04 => 1 FROM ubuntu:16.04 => 0 FROM...
done opening a bug report at ubuntu launchpad for "coreutils". https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1791983 Attaching a simplified version of the testscript. [bin_kill_broken.sh](https://github.com/gdraheim/docker-systemctl-replacement/files/2371968/bin_kill_broken.sh.txt)
As noted in the ubuntu ticket, the tool /bin/kill is really coming from the "procps" package. == apt-file bin/kill ubuntu:14.04 APTFILE procps: /bin/kill ubuntu:14.04 MANPAGE procps-ng October 2011 KILL(1) ubuntu:16.04...
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1791983 No update on the bug ticket within a month. It may be left broken in Ubuntu 16.04 LTS.
Another month has passed without a hint. Ubuntu 16.04 LTS will be kept broken?