A NOTE has been added to this issue. ====================================================================== https://austingroupbugs.net/view.php?id=1789 ====================================================================== Reported By: Mark_Galeck Assigned To: ====================================================================== Project: 1003.1(2016/18)/Issue7+TC2 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 Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2023-11-22 02:24 UTC Last Modified: 2023-11-22 06:20 UTC ====================================================================== Summary: if command name contains slash, it cannot be arg0 for execl() ======================================================================
---------------------------------------------------------------------- (0006579) larryv (reporter) - 2023-11-22 06:20 https://austingroupbugs.net/view.php?id=1789#c6579 ---------------------------------------------------------------------- It is not true that "line 29495 says arg0 points to a filename". What it says is that "[the] argument <i>arg0</i> <b>should</b> point to a filename string" (emphasis mine). That is a recommendation; as far as I can tell, the standard does not actually impose a semantic requirement on <i>arg0</i>. 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 ======================================================================
