--- Begin Message ---
|
Subject: |
"kill -l" doesn't conform to POSIX when POSIXLY_CORRECT is set |
|
Date: |
Sun, 11 Sep 2011 01:25:38 -0700 |
|
User-agent: |
SquirrelMail/1.4.21 |
>From http://pubs.opengroup.org/onlinepubs/9699919799/utilities/kill.html:
When the -l option is specified, the symbolic name of each signal shall
be written in the following
format:
"%s%c", <signal_name>, <separator>
where the <signal_name> is in uppercase, without the SIG prefix, and the
<separator> shall be
either a <newline> or a <space>. For the last signal written,
<separator> shall be a <newline>.
"kill -l" currently prints a table with each signal preceded by its number
and with the SIG prefixes, even with POSIXLY_CORRECT.
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#9473: "kill -l" doesn't conform to POSIX when POSIXLY_CORRECT is set |
|
Date: |
Sun, 11 Sep 2011 16:09:49 -0700 |
|
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.21) Gecko/20110831 Thunderbird/3.1.13 |
Typically, 'kill' is built into the shell, and you're undoubtedly
invoking your shell's version of kill. So you need to send a bug report
to your shell's maintainer, not to coreutils'.
For example, on my host:
$ /home/eggert/opt/Linux-x86_64/coreutils-8.13/bin/kill -l | head -n 1
HUP
$ kill -l | head -n 1
1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL 5) SIGTRAP
So coreutils conforms, but the shell does not.
--- End Message ---