Minutes of the 26th July 2018 Teleconference Austin-877 Page 1 of 1 Submitted by Geoff Clare, The Open Group. 27th July 2018 Attendees: Don Cragun, IEEE PASC OR Mark Ziegast, SHware Systems Dev. Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Geoff Clare, The Open Group Eric Blake, Red Hat Joerg Schilling, FOKUS Fraunhofer Apologies: Andrew Josey, The Open Group Richard Hansen, Google Martin Rehak, Oracle, The Open Group OR * General news No news * Outstanding actions (Please note that this section has been flushed to shorten the minutes - to locate the previous set of outstanding actions, look to the minutes from 9 March 2018 and earlier) * Current Business Bug 1077: Recommend support for wide-character regcomp and regexec and/or specify multi-byte behavior OPEN http://austingroupbugs.net/bug_view_page.php?bug_id=1077 Andrew has completed the action to ping his Apple contact and is awaiting a reply. Bug 1118: Clarify meaning of "file lock" Accepted as Marked http://austingroupbugs.net/view.php?id=1118 This item is tagged for TC3-2008. On page 60 line 1795 section 3 add a new subsection: 3.168 File Lock A lock obtained on a file through the use of fcntl() or lockf(). and renumber the later 3.x subsections. On page 874 after line 29515, add to flockfile APPLICATION USAGE: Note: a FILE lock is not a file lock (see XREF to XBD 3.168). On page 875 line 29518 section flockfile(), change: acquire a file lock to: acquire a FILE lock Bug 1119: When the file named by the operand does not exist, `file` should not exit with zero status Rejected http://austingroupbugs.net/view.php?id=1119 The standard clearly states that this is not an error (see page 2790, line 91651-3): If the file named by the file operand does not exist, cannot be read, or the type of the file named by the file operand cannot be determined, this shall not be considered an error that affects the exit status The file utility is unlike other file-handling utilities in that when a file does not exist, its non-existence is a piece of information about the file which file writes to standard output. The exit status of zero indicates that this information was successfully written to standard output. Other utilities report the non-existence to standard error and the exit status indicates that an error message was written to standard error. Next Steps ---------- The next call is on August 2nd 2018 (a Thursday) We will start with bug 1120. Apologies in Advance: Andrew Josey (2018-08-02, 2018-08-09, 2018-08-23) Martin Rehak (until 2018-08-02) Geoff Clare (2018-08-16) Calls are anchored on US time. (8am Pacific) This call will be for the regular 90 minutes. http://austingroupbugs.net An etherpad is usually up for the meeting, with a URL using the date format as below: https://posix.rhansen.org/p/201x-mm-dd username=posix password=2115756#