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:
I am not able to signal a group of processes. Wrt kill(1), by specifying negative PID, kill should send signal to the process group.

Version-Release number of selected component (if applicable):
util-linux-ng-2.17.2-12.4.el6.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. create a process group (parent, several children)
2. kill -s SIGTERM -- -PID_OF_PARENT
  
Actual results:
bash: kill: (-PID_OF_PARENT) - No such process

Expected results:
Process group should have been signalled.

Created attachment 579856 [details]
Usage example in C

The program should signal a process group by the signal specified in the first argument.

Actual result is: kill: No such process

Same, as /bin/kill.

Kernel used: 2.6.32-232.el6.x86_64

(In reply to comment #2)
>
> Created attachment 579856 [details]

this test-case can't demonstrate the bug, it simply does sys_kill().

> The program should signal a process group by the signal specified in the first
> argument.

Yes, but pgid should be correct.

> Actual result is: kill: No such process
> 
> Same, as /bin/kill.

I do not have the testing machine with rhel right now, but I simply
can't believe it has the bug like this ;) I bet it would have been
noticed a long ago.

Could you please double check? Or could you provide the "complete"
test-case? Or, simply, could you show how did you verify that
kill -pgid doesn't work?

Or. could you try the simplest test-case:

    $ perl -wle '$SIG{CONT}=sub{print $$}; fork ? wait : kill "CONT", -getppid'

on my machine the output is:

    5398
    5399

which shows that kill -pgid works correctly.

Oleg, thank you for your reply. The problem was in misunderstanding of the process group.