A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1789 
====================================================================== 
Reported By:                Mark_Galeck
Assigned To:                
====================================================================== 
Project:                    Issue 8 drafts
Issue ID:                   1789
Category:                   Shell and Utilities
Type:                       Error
Severity:                   Objection
Priority:                   normal
Status:                     New
Name:                       Mark Galeck 
Organization:                
User Reference:              
Section:                    Volume 2, Chapter 3 
Page Number:                865, 2487 
Line Number:                80936, 29495 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2023-11-22 02:24 UTC
Last Modified:              2023-11-22 09:42 UTC
====================================================================== 
Summary:                    if command name contains slash, it cannot be arg0
for execl()
====================================================================== 

---------------------------------------------------------------------- 
 (0006581) Guy Harris (reporter) - 2023-11-22 09:42
 https://austingroupbugs.net/view.php?id=1789#c6581 
---------------------------------------------------------------------- 
Perhaps the paragraph containing line 29495 should :-) note that, to use
IETF RFC 2119 terminology:

1. MUST   This word, or the terms "REQUIRED" or "SHALL", mean that the
   definition is an absolute requirement of the specification.

2. MUST NOT   This phrase, or the phrase "SHALL NOT", mean that the
   definition is an absolute prohibition of the specification.

3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.

4. SHOULD NOT   This phrase, or the phrase "NOT RECOMMENDED" mean that
   there may exist valid reasons in particular circumstances when the
   particular behavior is acceptable or even useful, but the full
   implications should be understood and the case carefully weighed
   before implementing any behavior described with this label.

5. MAY   This word, or the adjective "OPTIONAL", mean that an item is
   truly optional.  One vendor may choose to include the item because a
   particular marketplace requires it or because the vendor feels that
   it enhances the product while another vendor may omit the same item.
   An implementation which does not include a particular option MUST be
   prepared to interoperate with another implementation which does
   include the option, though perhaps with reduced functionality. In the
   same vein an implementation which does include a particular option
   MUST be prepared to interoperate with another implementation which
   does not include the option (except, of course, for the feature the
   option provides.)

code calling exec() SHOULD make arg0 point to point to a filename string
that is associated with the process being started by one of the exec
functions, but that programs MUST NOT assume that argv[0], as passed to
main(), will be such a string, without an agreement between the program
calling execl() and the program being executed by execl() to that effect.

For what it's worth, at least on macOS Ventura, bash, ksh, dash, and zsh
all provide an argv[0] that is equal to the string used to invoke the
program, i.e., with a program "arg0", in /tmp, which prints out the value
of argv[0]:

./arg0, when run in /tmp, prints "./arg0";
arg0, when run with a PATH that includes "." prints "arg0";
/tmp/arg0 prints "/tmp/arg0". 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2023-11-22 02:24 Mark_Galeck    New Issue                                    
2023-11-22 02:24 Mark_Galeck    Name                      => Mark Galeck     
2023-11-22 02:24 Mark_Galeck    Section                   => Volume 2, Chapter 3
2023-11-22 02:24 Mark_Galeck    Page Number               => 865, 2487       
2023-11-22 02:24 Mark_Galeck    Line Number               => 80936, 29495    
2023-11-22 06:20 larryv         Note Added: 0006579                          
2023-11-22 07:18 Don Cragun     Note Added: 0006580                          
2023-11-22 07:19 Don Cragun     Project                 
1003.1(2016/18)/Issue7+TC2 => Issue 8 drafts
2023-11-22 07:21 Don Cragun     version                   => Draft 3         
2023-11-22 09:42 Guy Harris     Note Added: 0006581                          
======================================================================


  • [Issue 8 d... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issu... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issu... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issu... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issu... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issu... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issu... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issu... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issu... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [Issu... Austin Group Issue Tracker via austin-group-l at The Open Group

Reply via email to