Minutes of the 22 January 2015 Teleconference Austin-690 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 23 January 2015 Attendees: David Clissold, IBM Andrew Josey, The Open Group Mark Ziegast, SHware Systems Martin Rehak, Oracle, The Open Group OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Joerg Schilling, FOKUS Fraunhofer Geoff Clare, The Open Group Richard Hansen, BBN Mark Brown, Canonical Don Cragun, IEEE PASC OR Eric Blake, Red Hat * General news On the PASC PAR approval progress - still open. Don currently has the action to progress. There has been some offline discussions between Don, Joe Gwinn and Andrew about the PASC policies & procedures. Richard reported that he is investigating how IEEE can obtain the posix.org domain. * Outstanding actions +Bug 0000251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames OPEN http://austingroupbugs.net/view.php?id=251 Don has an action to produce a proposal. +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 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, David to AIX and Jim to Solaris. Jim has completed his action (see bugnote 1691). Andrew should chase HP and Apple for input. +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. Bug 696 either NAME_MAX shouldn't be optional, or readdir_r() needs clarification http://www.austingroupbugs.net/view.php?id=696 Don has an action to propose a resolution. Bug 0000721: Internal storage vs static storage OPEN http://austingroupbugs.net/view.php?id=721 This item is still open. Bug 0000375: Extend test/[...] conditionals: ==, <, >, -nt, -ot, -ef OPEN http://austingroupbugs.net/view.php?id=375 This is still left open due to discussions pending on the reflector. Bug 0000789: Add set -o pipefail OPEN http://austingroupbugs.net/view.php?id=789 * Current Business Bug #881: add ppoll() OPEN http://austingroupbugs.net/view.php?id=881 Martin has completed his action to ask The Open Group Base Working Group if they will sponsor ppoll(). Bug #882: 882: meaning of "utility syntax error" unclear Accepted as marked. http://austingroupbugs.net/view.php?id=882 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 standard is unclear on what constitutes a "Shell Error". Notes to the Editor (not part of this interpretation): On page 2337 lines 74285-74287 (XCU 2.8.1 Consequences of Shell Errors), change: For a non-interactive shell, an error condition encountered by a special built-in (see Section 2.14) or other type of utility shall cause the shell to write a diagnostic message to standard error and exit as shown in the following table: to: Certain errors shall cause the shell to write a diagnostic message to standard error and exit as shown in the following table: On page 2337 lines 74288-74295 (XCU 2.8.1 Consequences of Shell Errors table), change: Error | Special Built-In | Other Utilities ------------------------------------------------------------ Shell language syntax error | Shall exit | Shall exit Utility syntax error (option or operand error) | Shall exit | Shall not exit Redirection error | Shall exit | Shall not exit Variable assignment error | Shall exit | Shall not exit Expansion error | Shall exit | Shall exit Command not found | N/A | May exit Dot script not found | Shall exit | N/A to: Error | Non-Interactive Shell | Interactive Shell | Shell Diagnostic Message Required ------------------------------------------------------------------- Shell language syntax error | shall exit | shall not exit | yes Special built-in utility error | shall exit | shall not exit | no(1) Other utility (not a special built-in) error | shall not exit | shall not exit | no(2) Redirection error with special built-in utilities | shall exit | shall not exit | yes Redirection error with compound commands | may exit(3) | shall not exit | yes Redirection error with function execution | may exit(3) | shall not exit | yes Redirection error with other utilities (not special built-ins) | shall not exit | shall not exit | yes Variable assignment error | shall exit | shall not exit | yes Expansion error | shall exit | shall not exit | yes Command not found | may exit | shall not exit | yes Notes: (1) Although special built-ins are part of the shell, a diagnostic message written by a special built-in is not considered to be a shell diagnostic message, and can be redirected like any other utility. (2) The shell is not required to write a diagnostic message, but the utility itself shall write a diagnostic message if required to do so. (3) A future version of this standard may require the shell to not exit in this condition. On page 2337 lines 74303-74304 (XCU 2.8.1 Consequences of Shell Errors), delete: In all of the cases shown in the table, an interactive shell shall write a diagnostic message to standard error without exiting. On page 2356 lines 75100-75104 (XCU 2.14 list item 1), change: A syntax error in a special built-in utility may cause a shell executing that utility to abort, while a syntax error in a regular built-in utility shall not cause a shell executing that utility to abort. (See Section 2.8.1 for the consequences of errors on interactive and non-interactive shells.) If a special built-in utility encountering a syntax error does not abort the shell, its exit value shall be non-zero. to: An error in a special built-in utility may cause a shell executing that utility to abort, while an error in a regular built-in utility shall not cause a shell executing that utility to abort. (See Section 2.8.1 for the consequences of errors on interactive and non-interactive shells.) If a special built-in utility encountering an error does not abort the shell, its exit value shall be non-zero. Bug #879: strptime is missing conversion specifiers described in strftime OPEN http://austingroupbugs.net/view.php?id=879 This item was not discussed at this call. We will continue this item on the next call. Action for Joerg from last call : Test %Z side effects and other results for the last OpenSolaris version Next Steps ---------- The next call is on January 29, 2015 (a Thursday) Calls are anchored on US time. (8am Pacific) This call will be for the regular 90 minutes. http://austingroupbugs.net An IRC channel will be available for the meeting irc://irc.freenode.net/austingroupbugs An etherpad is usually up for the meeting, with a URL using the date format as below: http://posix@posix.rhansen.org:9001/p/201x-mm-dd password=2115756#