Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

man 1 kill shows -q option (Use  sigqueue(2)  rather  than kill(2) and the sigval argument is used to specify an integer to be sent with the signal.). But when executed, kill doesn't accept -q.

It is miss leading when the man page shows something and the behavior is something else.

Version-Release number of selected component (if applicable):


How reproducible:
This is a packaging issue, so it is 100% reproducible.


Actual results:

Executing only `kill` shows the usage, which doesn't contain -q option.

~/$ kill
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]


Expected results:

Executing only `kill` shows the usage, which doesn't contain -q option.

~/$ kill
kill: usage: kill [-s sigspec | -n signum | -sigspec | -q sigval] pid | jobspec ... or kill -l [sigspec]

Looks like HAVE_SIGQUEUE is never set to 1 anywhere in util-linux.

21-11-2016 10:09:38 arun-desk-r7 ~/code/personal/util-linux-2.29
$ grep HAVE_SIGQUEUE -rw . -n                                   
./config.h.in:395:#undef HAVE_SIGQUEUE                          
./misc-utils/kill.c:74:#ifdef HAVE_SIGQUEUE                     
./misc-utils/kill.c:311:#ifdef HAVE_SIGQUEUE                    
./misc-utils/kill.c:388:#ifdef HAVE_SIGQUEUE                    
./misc-utils/kill.c:406:#ifdef HAVE_SIGQUEUE                    
./misc-utils/kill.c:453:#ifdef HAVE_SIGQUEUE                    
21-11-2016 10:09:44 arun-desk-r7 ~/code/personal/util-linux-2.29

> ~/$ kill
> kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill > -l [sigspec]

It seems like you're talking about shell built-in kill command rather than about util-linux kill binary, try

  /usr/bin/kill --help

and it works for me:

# strace /usr/bin/kill --queue 123 --signal ALRM 31622
...
rt_sigqueueinfo(31622, SIGALRM, {si_signo=SIGALRM, si_code=SI_QUEUE, si_pid=31630, si_uid=0, si_value={int=123, ptr=0x7b00000000}}) = 0
...

# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.3 (Maipo)