Minutes of the 20th March 2023 Teleconference Austin-1300 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 23rd March 2023 Attendees: Don Cragun, IEEE PASC OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Andrew Josey, The Open Group Eric Blake, Red Hat, The Open Group OR Geoff Clare, The Open Group Eric Ackermann, HPI, University of Potsdam Tom Thompson, IEEE Mark Ziegast, SHware Systems Dev. * General news A release candidate of draft 3 is now available. Andrew took an action to draft a set of reviewers notes (in progress after the meeting, and sent to the core team). We need to complete final process approvals to get the ballots underway. * Carried Forward This section trimmed -- see Austin/1264 Bug 1406: clarification of SEEK_END when current pointer doesn't match buffer size OPEN https://austingroupbugs.net/view.php?id=1406 Actions carried forward: ACTION: Andrew to contact Rich Felker (dalias) and Alan Coopersmith (Solaris) for feedback. Completed ACTION: Eric B to contact glibc folks. Bug 1616: Standardize mktemp utility OPEN https://austingroupbugs.net/view.php?id=1616 We will need a sponsor; it is not suitable for inclusion in Issue 8. ACTION: Eric to ask The Open Group to sponsor adding the mktemp utility (for Issue 9). Bug 1291: Add method to obtain pthread attributes OPEN https://austingroupbugs.net/view.php?id=1291 Needs additional details and sponsor for Issue 9 Bug 0000251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames OPEN http://austingroupbugs.net/view.php?id=251 (brought forward) Don has an action to produce a proposal. Bug 1622: Standardize getpeereid function OPEN https://austingroupbugs.net/view.php?id=1622 Action: Eric B to ask The Open Group if they are willing to sponsor this function for Issue 9. * Current Business Bug 1630: Alias names https://austingroupbugs.net/view.php?id=1630 OPEN We discussed this at length and a proposal has been entered into the etherpad for feedback. See https://posix.rhansen.org/p/2023-02-27 Bug 1629: Shell vs. read(2) errors on the script Accepted as Marked. https://austingroupbugs.net/view.php?id=1629 This item is tagged for Issue 8. Add a row (D2.1 p2330) to the table in 2.8.1 Consequences of Shell Errors: Unrecoverable read error when reading commands | shall exit *4 | shall exit *4 | yes and add a new note after the table: 4. If an unrecoverable read error occurs when reading commands, other than from the file operand of the dot special built-in, the shell shall execute no further commands (including any already successfully read but not yet executed) other than any specified in a previously defined EXIT trap action. An unrecoverable read error while reading from the file operand of the dot special built-in shall be treated as a special built-in utility error. Change P3155, L107009-107011 in the exit status section of the sh utility from: 1-125 A non-interactive shell detected an error other than command_file not found or executable, including but not limited to syntax, redirection, or variable assignment errors. to: 1-125 A non-interactive shell detected an error other than command_file not found, command_file not executable, or an unrecoverable read error while reading commands (except from the file operand of the dot special built-in); including but not limited to syntax, redirection, or variable assignment errors. Add to the exit status section of the sh utility on P3155 after L107014: 128 An unrecoverable read error was detected while reading commands, except from the file operand of the dot special built-in. On D2.1 page 358 line 12462 section (RATIONALE), change: Exit statuses of 126, 127, and greater than 128 are ambiguous in certain circumstances because they have special meanings in the shell (see [xref to XCU 2.8.2]). to: Exit statuses of 126 and greater are ambiguous in certain circumstances because they have special meanings in the shell (see [xref to XCU 2.8.2] and the EXIT STATUS section of [xref to XCU sh]). On D2.1 page 359 line 12469 section (RATIONALE), delete: The value 128 is disallowed for simplicity, making the allowed values 1 to 125 inclusive rather than 1 to 125 inclusive and 128. After D2.1 page 531 line 18867 section _Exit() (APPLICATION USAGE), add a new paragraph: Exit statuses of 126 and greater are ambiguous in certain circumstances because they have special meanings in the shell (see [xref to XCU 2.8.2] and the EXIT STATUS section of [xref to XCU sh]). After D2.1 page 789 line 27009 section exit() (APPLICATION USAGE), add a new paragraph (after applying bug 1490): See also _Exit(). On D2.1 page 2370 line 76769 section exit (RATIONALE), change: As explained in other sections, certain exit status values have been reserved for special uses and should be used by applications only for those purposes: 126 A file to be executed was found, but it was not an executable utility. 127 A utility to be executed was not found. >128 A command was interrupted by a signal. to: As explained in other sections, certain exit status values have been reserved for special uses and should be used by applications only for those purposes: 126 A file to be executed was found, but it was not an executable utility. 127 A utility to be executed was not found. 128 An unrecoverable read error was detected by the shell while reading commands, except from the file operand of the dot special built-in. >128 A command was interrupted by a signal. On page 3238 line 110033 section tsort (RATIONALE), after applying bug 1617 change: Implementations are urged to set the implementation-defined maximum number of cycles reported via the exit status to at most 125, leaving 128 for other errors, and leaving 126, 127, and values greater than 128 to have the special meanings that the shell assigns to them. (An implementation that wants to distinguish other types of errors would need to set the maximum to less than 125 so that 128 is not the only code available for those errors). to: Implementations are urged to set the implementation-defined maximum number of cycles reported via the exit status to at most 124, leaving values above that maximum through 125 for other errors, and leaving values 126 and greater to have the special meanings that the shell assigns to them. We will start at bug 1641 next time. Next Steps ---------- The next calls are on: Thu 2023-03-23 (general bugs) Mon 2023-03-27 (general bugs) Tentative depending if we have business The calls are for 90 minutes Calls are anchored on US time. (8am Pacific) 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)