The following issue has been SUBMITTED.
======================================================================
https://www.austingroupbugs.net/view.php?id=1744
======================================================================
Reported By: nrk
Assigned To:
======================================================================
Project: Issue 8 drafts
Issue ID: 1744
Category: Base Definitions and Headers
Type: Enhancement Request
Severity: Editorial
Priority: normal
Status: New
Name: Nickolas Raymond Kaczynski
Organization:
User Reference:
Section: 2.4.3 Signal Actions
Page Number: n/a
Line Number: n/a
Final Accepted Text:
======================================================================
Date Submitted: 2023-06-10 07:16 UTC
Last Modified: 2023-06-10 07:16 UTC
======================================================================
Summary: Explicitly require killpg to be async-signal-safe
Description:
Description of killpg() states:
If pgrp is greater than 1, killpg(pgrp, sig) shall be equivalent to
kill(-pgrp, sig).
And since kill() is async-signal-safe, killpg() should be as well but it's
not listed as such explicitly.
Desired Action:
Explicitly add killpg() to the list of async-signal-safe functions.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2023-06-10 07:16 nrk New Issue
2023-06-10 07:16 nrk Name => Nickolas Raymond
Kaczynski
2023-06-10 07:16 nrk Section => 2.4.3 Signal
Actions
2023-06-10 07:16 nrk Page Number => n/a
2023-06-10 07:16 nrk Line Number => n/a
======================================================================
