0001744: Explicitly require killpg to be async-signal-safe

ID	Project	Category	View Status	Date Submitted	Last Update

0001744	Issue 8 drafts	Base Definitions and Headers	public	2023-06-10 07:16	2024-06-11 09:12

Reporter	nrk	Assigned To
Priority	normal	Severity	Editorial	Type	Enhancement Request
Status	Closed	Resolution	Accepted
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

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
2023-07-20 23:50	Don Cragun	Page Number	n/a => 517
2023-07-20 23:50	Don Cragun	Line Number	n/a => 18354
2023-07-20 23:50	Don Cragun	Product Version	=> Draft 3
2023-07-24 15:49	Don Cragun	Status	New => Resolved
2023-07-24 15:49	Don Cragun	Resolution	Open => Accepted
2023-07-24 15:50	Don Cragun	Tag Attached: issue8
2023-08-22 14:28	geoffclare	Status	Resolved => Applied
2023-08-22 14:29	geoffclare	Tag Attached: applied_after_i8d3
2024-06-11 09:12	agadmin	Status	Applied => Closed