Minutes of the 18th July 2013 Teleconference Austin-619 Page 1 of 1 Submitted by Geoff Clare, The Open Group. 19th July 2013 Attendees Nick Stoughton, USENIX, ISO/IEC OR Don Cragun, PASC OR Geoff Clare, The Open Group Eric Blake, Red Hat Joerg Schilling, Fraunhofer Society Richard Hansen, BBN David Clissold, IBM Mark Brown, IBM Apologies Andrew Josey, The Open Group Jim Pugsley, Oracle * General news David let us know that we can use his conference number for future calls. He will let Andrew know the details. * Outstanding actions +Bug 0000561: NUL-termination of sun_path in Unix sockets OPEN http://austingroupbugs.net/view.php?id=561 Eric has an action to update the proposal. +Bug 0000573: Please add '+' to the portable filename character set OPEN http://austingroupbugs.net/view.php?id=573 Joerg has an action to prepare a proposed change. +Bug 0000592: consistent use of struct timespec OPEN http://austingroupbugs.net/view.php?id=592 Jim had provided additional information in bugnote 1627. This was discussed and Jim took an action to provide further information. +Bug 0000598: OH shading and new interfaces OPEN http://austingroupbugs.net/view.php?id=598 Eric has an action to propose a new solution with self-contained headers. +Bug 0000517: EBNF support OPEN http://austingroupbugs.net/view.php?id=517 Action on Joerg to look at this. +Bug 0000633: SIGEV_THREAD delivery renders many signal interfaces unsafe OPEN http://austingroupbugs.net/view.php?id=633 We noted that feedback has settled down on the mailing list, and will discuss next session. +Bug 0000657: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified OPEN http://austingroupbugs.net/view.php?id=657 Eric has an action to propose wording to clarify the behavior for fmemopen(), and also to contact the glibc developers to get their feedback. +Bug 0000658: Undefined/unspecified behavior clauses in description of open have race conditions OPEN http://austingroupbugs.net/view.php?id=658 It was noted that there is some overlap with changes in TC1. Eric took an action to update the proposal to resolve the overlaps appropriately. +Bug 0000615: pthread_setcancelstate should be async-signal-safe OPEN http://austingroupbugs.net/view.php?id=615 We now have reports on AIX and Apple. Jim to report back on whether pthread_cancelstate() is async-signal-safe on Solaris. Andrew to ask HP whether pthread_cancelstate() is async-signal-safe on HP-UX. +Bug 622 left open pending resolution of 615. http://austingroupbugs.net/view.php?id=622 +Bug 0000672: Necessary step(s) to synchronize filename operations on disk OPEN http://austingroupbugs.net/view.php?id=672 Geoff has a new proposed resolution in note 1618. Decided to solicit input from FS developers. Eric to go to Linux, Mark to AIX and Jim to Solaris. +Bug 0000663: Specification of str[n]casecmp is ambiguous reopened http://austingroupbugs.net/view.php?id=663 Action on David to follow up with the IBM developers about the EBCDIC collation sequence. * Current Business Bug 0000717: meaning of "the shell shall exit" in a subshell environment Accept as Marked http://austingroupbugs.net/view.php?id=717 This item is tagged for TC2-2008 An interpretation is required. Interpretation response ------------------------ The standard is unclear on this issue, and no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale: ------------- The changes made here make the standard reflect existing practice. Notes to the Editor (not part of this interpretation): ------------------------------------------------------- Make the changes suggested in Note: 0001673. [copied below] At page 2370 line 75508 change: The exit utility shall cause the shell to exit with the exit status specified by the unsigned decimal integer n. to: The exit utility shall cause the shell to exit from its current execution environment with the exit status specified by the unsigned decimal integer n. If the current execution environment is a subshell environment, the shell shall exit from the subshell environment with the specified exit status and continue in the environment from which that subshell environment was invoked, otherwise the shell utility shall terminate with the specified exit status. After page 2371 line 75546 section 2.14 exit add to EXAMPLES: Propagate error handling from within a subshell: ( command1 || exit 1 command2 || exit 1 exec command3 ) > outputfile || exit 1 echo "outputfile created successfully" At page 2337 line 74300 section 2.8.1 change If any of the errors shown as "shall exit" or "(may) exit" occur in a subshell, the subshell shall (respectively may) exit with a non-zero status, but the script containing the subshell shall not exit because of the error. In all of the cases shown in the table, an interactive shell shall write a diagnostic message to standard error without exiting. to: If any of the errors shown as "shall exit" or "(may) exit" occur in a subshell environment, the shell shall (respectively may) exit from the subshell environment with a non-zero status and continue in the environment from which that subshell environment was invoked. In all of the cases shown in the table, an interactive shell shall write a diagnostic message to standard error without exiting and without any further processing of the command in which the error occurred. At page 2337 line 74312 section 2.8.2 change: If a command fails during word expansion or redirection, its exit status shall be greater than zero. to: If a command fails during word expansion or redirection, its exit status shall be between 1 and 125 inclusive. At page 2381 line 75846 section 2.14 set change: the shell immediately shall exit with the following exceptions to: the shell immediately shall exit, as if by executing the exit special built-in utility with no arguments, with the following exceptions At page 2382 line 75903 section 2.14 set change the description of the -u option to: When the shell tries to expand an unset parameter other than the '@' and '*' special parameters, it shall write a message to standard error and the expansion shall fail with the consequences specified in 2.8.1 Consequences of Shell Errors (on page 2337). Bug 0000721: Internal storage vs static storage OPEN http://austingroupbugs.net/view.php?id=721 Action: Don to propose changes to remove references to internal or static storage and replace with wording more like the setlocale() RETURN VALUE section (which uses neither term: "The application shall not modify the string returned. The returned string pointer might be invalidated or the string content might be overwritten by a subsequent call to setlocale()."). Bug 0000722: pthread_rwlock writers preferrence Accept as Marked http://austingroupbugs.net/view.php?id=722 This item is tagged for TC2-2008 An interpretation is required. Interpretation response ------------------------ The standard is unclear on this issue, and no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale: ------------- Changes were made to the read locks in Issue 6, that should also be represented in the write lock specification regarding read/write precedence. Notes to the Editor (not part of this interpretation): ------------------------------------------------------- On Page 1697: Remove line 54885: Implementations may favor writers over readers to avoid writer starvation. Bug 0000723: time is not allowed to write error messages to stderr Accept as Marked http://austingroupbugs.net/view.php?id=723 This item is tagged for TC2-2008 An interpretation is required. Interpretation response ------------------------ The standard states that time may only output timing statistics, not diagnostics, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: ------------- Existing practice includes the possibility of diagnostics, and also the possibility of no timing when only diagnostics appear. Notes to the Editor (not part of this interpretation): ------------------------------------------------------- Make the changes in Note: 0001685 [copied below] Change: The standard error shall be used to write the timing statistics. If -p is specified, the following format shall be used in the POSIX locale: to: If the utility utility is invoked, the standard error shall be used to write the timing statistics and may be used to write a diagnostic message if the utility terminates abnormally; otherwise the standard error shall be used to write diagnostic messages and may also be used to write the timing statistics. If -p is specified, the following format shall be used for the timing statistics in the POSIX locale: Next Steps ---------- The next call is on August 1, 2013 (a Thursday) Calls are anchored on US time. This call will be for the regular 90 minutes. An agenda item for the call is to decide how to update bug 267 so that it does not undo the bug 723 TC2 change when it is applied in Issue 8. There will be no call on July 25 2013. http://austingroupbugs.net We will use either the webex bridge or David Clissold's bridge. See the calendar for the list of dialup numbers. An IRC channel will be available for the meeting irc://irc.freenode.net/austingroupbugs