Subject: bug#9473: closed (Re: bug#9473: "kill -l" doesn't conform to POSIX when POSIXLY_CORRECT is set)

From: [email-masked] (GNU bug Tracking System)
Date: Sun, 11 Sep 2011 23:15:03 +0000

Your bug report

#9473: "kill -l" doesn't conform to POSIX when POSIXLY_CORRECT is set

which was filed against the coreutils package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
9473: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9473
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#9473: "kill -l" doesn't conform to POSIX when POSIXLY_CORRECT is set
From: Paul Eggert <[email-masked]>
To: [email-masked]
Cc: [email-masked]
Date: Sun, 11 Sep 2011 16:09:49 -0700
List-Id: <debbugs-submit.debbugs.gnu.org>

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.

Subject: "kill -l" doesn't conform to POSIX when POSIXLY_CORRECT is set
From: [email-masked]
To: [email-masked]
Date: Sun, 11 Sep 2011 01:25:38 -0700
List-Id: <debbugs-submit.debbugs.gnu.org>

>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.