Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
0001744 |
[Issue 8 drafts] Base Definitions and Headers |
Editorial |
Enhancement Request |
2023-06-10 07:16 |
2024-06-11 09:12 |
|
Reporter |
nrk |
View Status |
public |
|
Assigned To |
|
Priority |
normal |
Resolution |
Accepted |
|
Status |
Closed |
|
Product Version |
Draft 3 |
|
Name |
Nickolas Raymond Kaczynski |
Organization |
|
User Reference |
|
Section |
2.4.3 Signal Actions |
Page Number |
517 |
Line Number |
18354 |
Final Accepted Text |
|
|
Summary |
0001744: 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. |
Tags |
applied_after_i8d3, issue8 |
|
Attached Files |
|
|