Minutes of the 20th October 2011 Teleconference Austin-540 Page 1 of 1 Submitted by Andrew Josey, The Open Group. October 22 , 2011 Attendees Andrew Josey, The Open Group Don Cragun, PASC OR Mark Brown, IBM, TOG OR Jim Pugsley, Oracle Geoff Clare, The Open Group Nick Stoughton, USENIX, ISO/IEC OR Eric Blake, Red Hat The TC1-2008 Draft 4 document is still progressing, with the final feedback from the IEEE Mandatory Editorial Coordination review being received. Cathy continues to merge the changes into the BaseI7 tree and that is still a work in progress, although due to other workload has been progressing slower than we would have liked. It was agreed that we should target the IEEE and ISO ballot for January 2012, and that we will complete the merger of current changes in December. This will allow some sanity checking of the changes prior to the main ballot. Andrew had sent a note about the POSIX C++ binding project PAR being about to timeout to the PASC SEC but had only one response. He has sent a followup note to the SEC assuming that no response is agreement that it should be withdrawn. * New Business Bug 0000498: During process termination, open file descriptors should be closed as if by appropriate calls to close() Accepted as marked. http://austingroupbugs.net/view.php?id=498 This item is tagged for TC2-2008 Append the following to the last paragraph in 2.9.7 (P516 L17869): The requirement on the close() function shall also apply whenever a file descriptor is successfully closed however caused (for example, as a consequence of calling close(), calling dup2(), or of process termination). Bug 0000499: xargs -L says when it means unescaped Accepted http://austingroupbugs.net/view.php?id=499 This item is tagged for TC2-2008 Bug 0000500: Special meaning of inside double quotes OPEN http://austingroupbugs.net/view.php?id=500 Bug 0000501: fdatasync() EBADF and "open for writing" Accepted as Marked http://austingroupbugs.net/view.php?id=501 This item is tagged for TC2-2008 An interpretation is required. Interpretation response The standard states that fdatasync() shall fail on a read-only file descriptor, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: The access mode of the file descriptor does not affect whether there are pending I/O operations on the underlying file. Notes to the Editor (not part of this interpretation): Make the changes in the Desired Action and Note: 0000994 In addition to the Desired Action, also make these changes: At line 27232 (APPLICATION USAGE), change "None." to: Note that even if the file descriptor is not open for writing, if there are any pending write requests on the underlying file, then that I/O will be completed prior to the return of fdatasync( ). Bug 0000502: XSI semaphore maximum value Accepted as Marked http://austingroupbugs.net/view.php?id=501 This item is tagged for Issue 8 An interpretation is required. Interpretation response The standard states that the maximum value for a semaphore is 32767, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: 0 is not a positive integer, and some implementations supply a larger maximum value. Notes to the Editor (not part of this interpretation): Implement changes in note Note: 0000997: At line 3095, change: ... a semaphore is a positive integer (0 through 32767). to: ... a semaphore is an integer with minimum value 0 and an implementation-defined maximum value which shall be at least 32767. We discussed mailing list items. Don agreed to take an action to followup on the prs utility email from Joerg. (completed after the meeting) Next Steps ---------- The next call is on November 3rd at 08:00 Pacific and will continue processing defect reports. This call will be for the regular 90 minutes. http://austingroupbugs.net See the calendar for the list of dialup numbers. An IRC channel will be available for the meeting irc://irc.freestandards.org #austin ICAL: http://www.google.com/calendar/ical/nvctqtstkuni3fab9k3jqtrt4g@group.calendar.google.com/public/basic XML: http://www.google.com/calendar/feeds/nvctqtstkuni3fab9k3jqtrt4g@group.calendar.google.com/public/basic