A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1341 
====================================================================== 
Reported By:                kre
Assigned To:                
====================================================================== 
Project:                    1003.1(2016)/Issue7+TC2
Issue ID:                   1341
Category:                   System Interfaces
Type:                       Error
Severity:                   Objection
Priority:                   normal
Status:                     New
Name:                       Robert Elz 
Organization:                
User Reference:              
Section:                    posix_spawn 
Page Number:                1452 ff.  
Line Number:                48227 ff.  
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2020-05-05 04:53 UTC
Last Modified:              2020-05-06 08:47 UTC
====================================================================== 
Summary:                    The resolution of
https://austingroupbugs.net/view.php?id=1208 as amended by
https://austingroupbugs.net/view.php?id=1208#c4830 is incorrect
====================================================================== 

---------------------------------------------------------------------- 
 (0004865) geoffclare (manager) - 2020-05-06 08:47
 https://austingroupbugs.net/view.php?id=1341#c4865 
---------------------------------------------------------------------- 
Re https://austingroupbugs.net/view.php?id=1341#c4858

The new specified behaviour is what naturally happens if posix_spawn() and
posix_spawnp() are implemented using fork and exec, as in the XRAT B.3.3
example implementation of posix_spawn() as amended by bug 1208. (This can
be turned into a posix_spawnp() implementation by doing a PATH loop around
the execve() call, if path does not contain any slashes.)

An implementation that chooses to make posix_spawn() a system call needs to
ensure the end result is the same as for a typical fork+exec
implementation. On such a system, presumably posix_spawnp() would be a C
library function that calls a posix_spawnp system call passing it the value
of PATH as an extra argument. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2020-05-05 04:53 kre            New Issue                                    
2020-05-05 04:53 kre            Name                      => Robert Elz      
2020-05-05 04:53 kre            Section                   => posix_spawn     
2020-05-05 04:53 kre            Page Number               => 1452 ff.        
2020-05-05 04:53 kre            Line Number               => 48227 ff.       
2020-05-05 05:07 kre            Note Added: 0004852                          
2020-05-05 05:09 kre            Note Deleted: 0004852                        
2020-05-05 08:18 geoffclare     Note Added: 0004853                          
2020-05-05 15:28 kre            Note Added: 0004858                          
2020-05-05 15:30 kre            Note Edited: 0004858                         
2020-05-05 17:36 kre            Note Edited: 0004858                         
2020-05-06 08:47 geoffclare     Note Added: 0004865                          
======================================================================


Reply via email to