kill: Broken support for querying multiple signal names

[BenWiederhake]

Example:

$ ../gnu/src/kill --version | head -n1
kill (GNU coreutils) 9.5
$ ../gnu/src/kill -l SIGUSR1 SIGUSR2
10
12
$ cargo run --all-features kill -l SIGUSR1 SIGUSR2
10
$

Note that the bash built-in kill also supports querying multiple names at the same time, but the Debian default binary (procps-ng 4.0.4) does not.

More issues found while checking #6201

• Signal names in all cases, i.e. SIGUSR1 vs. sIgUsR1: Moved to kill: signal names only understood in uppercase, should accept all casings #6217
• Missing RTMAX/RTMIN on Linux: Moved to kill: missing RTMAX/RTMIN on Linux #6218
• Table (-L) format is wrong: Moved to kill: Table output (-L) format is wrong #6219

[m-haisham]

Noticed that the gnu starts with 1 while uutils starts with 0.

--- STDOUT_GNU	
- 1 HUP      Hangup
+++ STDOUT_UUTILS
+ 0 EXIT

I'll change uutils to start with 1 as well if that's acceptable.

[m-haisham]

I'll post a pr for 3rd and a partial fix for 1st after #6201 has been merged.

The signal descriptions does not seem to be available for use in uucore atm. So probably best to add them in another pull request.

I am not sure about what should be done for the 2nd.

[tertsdiepraam]

@BenWiederhake, what's the status here. Can we close this with #6216 ? If not, should we maybe move the rest to separate issues?

[BenWiederhake]

Yeah, you're right, it should be separate issues. I was a bit too lazy when I created this issue :)

[BenWiederhake]

This particular issue was fixed by #6210.