[Bug 1791983] Re: kill -TERM exitcode regression 16.04

[C de-Avillez]

Hello Guido,

Thank you for opening this bug and helping make Ubuntu better.

As far as I can remember, Ubuntu has been using kill from the procps
package, not coreutils. On Cosmic and 16.04 (the only machines I have
access to right now), /bin/kill is being provided by procps:

cerdea at piatam:$ dpkg -L coreutils|grep kill
1 $ dpkg -L procps|grep kill
/bin/kill
/usr/bin/skill
/usr/share/man/man1/kill.1.gz
/usr/share/man/man1/skill.1.gz
/usr/bin/pkill
/usr/share/man/man1/pkill.1.gz

It is probable that this is also your case, but before changing the
package in the bug I would like you to check.

* man kill should tell you if it is coreutils or not;
* apt-file search bin/kill will return you all packages that deploy "bin/kill" (note that we are only looking for /bin/kill).

Please report back, and we will then act as needed.

** Changed in: coreutils (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1791983

Title:
  kill -TERM exitcode regression 16.04

Status in coreutils package in Ubuntu:
  Incomplete

Bug description:
  I had a regression error in one of my testsuites.
  https://github.com/gdraheim/docker-systemctl-replacement/issues/43

  After investigating I did find that the command "kill -TERM" behaves
  different in Ubuntu 16.04 in comparison to all other Ubuntu versions
  and in comparison to all other tested Linux distributions
  (opensuse,centos).

  ====> "kill -TERM" does report an exitcode=0 (OK) where it should say
  failed.

  Note that the testsuite of coreutils does define a behaviour of not-ok at
  http://git.savannah.gnu.org/cgit/coreutils.git/tree/tests/misc/kill.sh

  There you can see

      # params required
      returns_ 1 env kill || fail=1
      returns_ 1 env kill -TERM || fail=1

  However this is the result tested with the available docker images

     == kill
       ubuntu:14.04 => 1
       ubuntu:16.04 => 1
       ubuntu:18.04 => 1
       ubuntu:18.10 => 1
     == kill -TERM
       ubuntu:14.04 => 1
       ubuntu:16.04 => 0
       ubuntu:18.04 => 1
       ubuntu:18.10 => 1

  I am attaching the testscript that shows the results above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1791983/+subscriptions