Minutes of the 15th January 2024 Teleconference Austin-1376 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 17th January 2024 Attendees: Don Cragun, IEEE SA OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Mark Ziegast, SHware Systems Dev. Eric Ackermann Andrew Josey, The Open Group Eric Blake, Red Hat, The Open Group OR Levon Tumanyan Apologies Tom Thompson, IEEE Geoff Clare, The Open Group * General news Draft 4 is still in review at The Open Group and IEEE, with the review closing on January 31 2024. No comments have been received as yet. We discussed when the ISO/IEC draft is due to go to ballot. Andrew and Nick noted that is expected to be after the ballot on approving the use of line numbers concludes and that they would check with Bill Ash. * Current Business Bug 1789: if command name contains slash, it cannot be arg0 for execl() Accepted as Marked https://austingroupbugs.net/view.php?id=1789 On page 865 line 29495, 29499 change: (D4 p877 line 29519) ... should point to a filename string that is associated with the process being started by one of the exec functions. to: ... should point to a string that is associated with the with the filename of the process being started by one of the exec functions. and add to Application Usage, page 872 after line 29773: (D4 p874 line 29796) The string in arg0 or argv[0] is typically the basename of the path of the file being executed. However, there is no requirement in this standard that this is so, and the program executed will see this string in the first element of the argv[] array passed to its main() function, and may alter its functionality based on this. On page 872 Rationale, line 29785, change (D4 p874 line 29808) ... the first argument be a filename string associated with the process being started. Although some existing applications pass a pathname rather than a filename string in some circumstances, a filename string is more generally useful, since the common usage of argv[0] is in printing diagnostics. In some cases the filename passed is not the actual filename of the file; for example, many implementations of the login utility use a convention of prefixing a ('-') to the actual filename, which indicates to the command interpreter being invoked that it is a ``login shell’’. to: ... the first argument be simply a string associated with the filename of the process being started. Most applications pass a filename string or a pathname string, a filename string is more generally useful, since the common usage of argv[0] is in printing diagnostics. In some cases the filename in the string passed is not the actual filename of the file; for example, many implementations of the login utility use a convention of prefixing a ('-') to the actual filename, which indicates to the command interpreter being invoked that it is a ``login shell’’. Bug 1790: More info on *ALT* constants https://austingroupbugs.net/bug_view_page.php?bug_id=1790 We will continue on this item on the next call. Next Steps ---------- The next call is on: Thu 2024-01-18 (Zoom meeting - general bugs) Mon 2024-01-22 (Zoom meeting - general bugs) The calls are for 90 minutes Calls are anchored on US time. (8am Pacific) Apologies in Advance: Geoff Clare, 2024-01-15 to 2024-01-22 inclusive Please check the calendar invites for dial in details. Bugs are at: https://austingroupbugs.net An etherpad is usually up for the meeting, with a URL using the date format as below: https://posix.rhansen.org/p/20xx-mm-dd (For write access this uses The Open Group single sign on, for those individuals with gitlab.opengroup.org accounts. Please contact Andrew if you need to be setup)