Re: upstream bug fixes to procps
>> BTW, it is highly likely that your /bin/kill program is in violation
>> of the appropriate standards. I supply an alternative with procps that
>> you might want to consider using instead.
>
> Debian uses /bin/kill from our BSD utilities package (bsdutils) [1].
> If you would be kind to provide details on this, we could file a
> bug report and resolve it properly (by starting to use procps' kill).
> Thanks.
>
> [1] Source for which can be found at:
> ftp://ftp.debian.org/dists/slink/main/source/base/bsdutils_4.4.1.1.tar.gz
OK, you have several problems. I think it is funny that Red Hat and Debian
both ship with buggy kill commands, yet they do not share any source code.
Red Hat is using a GNU version that is actually more BSD-like than the BSD
code that Debian ships.
I'm looking at the Unix98 standard, which extends POSIX.
I'll start with a really minor issue. You are missing SIGPOLL, which is
a required signal.
These don't work properly:
kill -l 11
kill -l 139
Both should display "SEGV\n" as output. (not "SIGSEGV\n" like GNU kill)
The BSD code that Debian ships doesn't even support either command.
(note that 139 is the exit status of a command killed with SIGSEGV)
This doesn't work: kill -s KILL 5281
This doesn't work: kill -- 5320
BTW, there is a general Linux bug that prevents kill from being 100%
correct on the i386, m68k, ppc, and arm ports. We lack SIGSYS.
The alpha, mips, sparc, and sparc64 ports provide it and SIGEMT.
Reply to: