| To: | austin-group-l@xxxxxxxxxxxxx |
|---|---|
| Subject: | [1003.1(2008)/Issue 7 0000062]: Is it correct to list fork as an async-signal safe interface |
| From: | Austin Group Bug Tracker <noreply@xxxxxxxxxxxxx> |
| Date: | Fri, 9 Oct 2009 16:22:04 +0000 |
| Keywords: | [1003.1(2008)/Issue 7] System Interfaces |
The following issue has been UPDATED. ====================================================================== http://austingroupbugs.net/view.php?id=62 ====================================================================== Reported By: msbrown Assigned To: ajosey ====================================================================== Project: 1003.1(2008)/Issue 7 Issue ID: 62 Category: System Interfaces Type: Clarification Requested Severity: Comment Priority: normal Status: Interpretation Required Name: Mark Brown Organization: IBM User Reference: Section: 2.4.3 Page Number: 489 Line Number: 16723 Interp Status: Approved Final Accepted Text: http://austingroupbugs.net/view.php?id=62#c193 ====================================================================== Date Submitted: 2009-06-26 14:02 UTC Last Modified: 2009-10-09 16:22 UTC ====================================================================== Summary: Is it correct to list fork as an async-signal safe interface ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- has duplicate 0000018 _Fork() is needed to allow execution of... ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 2009-06-26 14:02 msbrown New Issue 2009-06-26 14:02 msbrown Status New => Under Review 2009-06-26 14:02 msbrown Assigned To => ajosey 2009-06-26 14:02 msbrown Name => Mark Brown 2009-06-26 14:02 msbrown Organization => IBM 2009-06-26 14:02 msbrown Section => 2.4.3 2009-06-26 14:02 msbrown Page Number => 489 2009-06-26 14:02 msbrown Line Number => 16723 2009-06-26 14:03 msbrown Note Added: 0000121 2009-06-26 14:06 msbrown Note Added: 0000122 2009-06-26 14:08 msbrown Relationship added has duplicate 0000018 2009-08-13 15:33 ajosey Interp Status => Pending 2009-08-13 15:33 ajosey Note Added: 0000193 2009-08-13 15:33 ajosey Status Under Review => Interpretation Required 2009-08-13 15:35 ajosey Final Accepted Text => http://austingroupbugs.net/view.php?id=62#c193 2009-08-13 15:35 ajosey Resolution Open => Accepted As Marked 2009-09-17 06:51 tahonermann Issue Monitored: tahonermann 2009-09-17 15:41 nick Interp Status Pending => Proposed 2009-10-09 16:21 ajosey Note Edited: 0000193 2009-10-09 16:22 ajosey Interp Status Proposed => Approved ====================================================================== |
| Previous by Date: | [1003.1(2008)/Issue 7 0000062]: Is it correct to list fork as an async-signal safe interface, Austin Group Bug Tracker |
|---|---|
| Next by Date: | [1003.1(2008)/Issue 7 0000062]: Is it correct to list fork as an async-signal safe interface, Austin Group Bug Tracker |
| Previous by Thread: | [1003.1(2008)/Issue 7 0000062]: Is it correct to list fork as an async-signal safe interface, Austin Group Bug Tracker |
| Next by Thread: | [1003.1(2008)/Issue 7 0000062]: Is it correct to list fork as an async-signal safe interface, Austin Group Bug Tracker |
| Indexes: | [Date] [Thread] [All Lists] |