A NOTE has been added to this issue. 
====================================================================== 
https://www.austingroupbugs.net/view.php?id=1674 
====================================================================== 
Reported By:                eblake
Assigned To:                
====================================================================== 
Project:                    1003.1(2016/18)/Issue7+TC2
Issue ID:                   1674
Category:                   Shell and Utilities
Type:                       Omission
Severity:                   Objection
Priority:                   normal
Status:                     New
Name:                       Eric Blake 
Organization:               Red Hat 
User Reference:             ebb.posix_spawnp 
Section:                    XSH posix_spawnp 
Page Number:                1455 
Line Number:                48328 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2023-04-19 02:35 UTC
Last Modified:              2023-04-19 17:12 UTC
====================================================================== 
Summary:                    may posix_spawnp() fail with ENOEXEC?
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0001208 calling chdir as part of posix_spawn
related to          0001044 Calling setsid as part of posix_spawn
====================================================================== 

---------------------------------------------------------------------- 
 (0006265) eblake (manager) - 2023-04-19 17:12
 https://www.austingroupbugs.net/view.php?id=1674#c6265 
---------------------------------------------------------------------- 
Another option might be to define a new POSIX_SPAWN_XXX flag to
posix_spawnattr_setflags() that gives finer-grained control over whether or
not to attempt a fallback to sh, and whether or not to attempt exit status
126 instead of 127 on ENOEXEC failures (when the failure is only detected
after a child process is created); but that would be more invention than
existing practice. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2023-04-19 02:35 eblake         New Issue                                    
2023-04-19 02:35 eblake         Name                      => Eric Blake      
2023-04-19 02:35 eblake         Organization              => Red Hat         
2023-04-19 02:35 eblake         User Reference            => ebb.posix_spawnp
2023-04-19 02:35 eblake         Section                   => XSH posix_spawnp
2023-04-19 02:35 eblake         Page Number               => 1455            
2023-04-19 02:35 eblake         Line Number               => 48328           
2023-04-19 02:35 eblake         Interp Status             => ---             
2023-04-19 12:16 eblake         Description Updated                          
2023-04-19 12:36 eblake         Note Added: 0006264                          
2023-04-19 12:36 eblake         Note Edited: 0006264                         
2023-04-19 13:25 eblake         Description Updated                          
2023-04-19 17:05 eblake         Relationship added       related to 0001208  
2023-04-19 17:06 eblake         Relationship added       related to 0001044  
2023-04-19 17:12 eblake         Note Added: 0006265                          
======================================================================


  • [1003.1(2016... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to