|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
|
0001362 |
[Issue 8 drafts] System Interfaces |
Editorial |
Error |
2020-07-03 09:35 |
2024-06-11 09:12 |
|
|
Reporter |
geoffclare |
View Status |
public |
|
|
Assigned To |
|
|
Priority |
normal |
Resolution |
Accepted |
|
|
Status |
Closed |
|
Product Version |
Draft 1 |
|
|
Name |
Geoff Clare |
|
Organization |
The Open Group |
|
User Reference |
|
|
Section |
posix_spawn() |
|
Page Number |
1428 |
|
Line Number |
47825-47851 |
|
Final Accepted Text |
|
|
|
Summary |
0001362: small editorial fixes to posix_spawn() |
|
Description |
In the ERRORS section there are several occurrences of:(or, if the error occurs after the calling process successfully returns, the child process shall exit with exit status 127)
This is intended to state a requirement (hence the use of "shall") and therefore should not be in parentheses. Only one occurrence is new in Issue 8 draft 1, but the others need to be fixed as well.
Another small editorial fix that doesn't seem worth submitting a separate bug for is a use of the phrase "relative file names".
|
|
Desired Action |
On page 1428 line 47825-47851 section posix_spawn(), change 6 occurrences of:... (or, if the error occurs after the calling process successfully returns, the child process shall exit with exit status 127). to:...; or, if the error occurs after the calling process successfully returns, the child process shall exit with exit status 127.
On page 1426 line 47733 section posix_spawn(), change:relative file names to:relative pathnames |
| Tags |
issue8 |
|
|
Attached Files |
|
|
|
Relationships 
