Minutes of the 26 January 2012 Teleconference Austin-547 Page 1 of 1 Submitted by Andrew Josey, The Open Group. January 27 , 2012 Attendees Andrew Josey, The Open Group Don Cragun, PASC OR Mark Brown, IBM, TOG OR Geoff Clare, The Open Group Nick Stoughton, USENIX, ISO/IEC OR Eric Blake, Red Hat Jim Pugsley, Oracle Apologies Joerg Schilling, Fraunhofer Society The TC1-2008 Draft 4 document merger into the Base Specs is still progressing, XBD, XCU and XRAT are now complete. * Old Business Bug 0000251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames OPEN http://austingroupbugs.net/view.php?id=251 Don reported that he was still working on a proposal to address this and related bugs, and that this bug will remain open until after TC1 is approved *New business Bug 0000529: fildes unspecified on close()'s [EINTR] Accepted as marked http://austingroupbugs.net/view.php?id=529 This item had been filed against the wrong Category. Mark completed his action to move the category from 2008-TC1 to 1003.1(2008)/Issue 7. 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: In order for multithreaded applications to be able to close file descriptors safely when close() might be interrupted, on EINTR close() must leave the file descriptor open so that close() can be called again. However, attempting to use the file descriptor might result in an error such as EIO. Notes to the Editor (not part of this interpretation): Change: If close() is interrupted by a signal that is to be caught, it shall return -1 with errno set to [EINTR] and the state of fildes is unspecified. to: If close() is interrupted by a signal that is to be caught, it shall return -1 with errno set to [EINTR] and fildes shall remain open; however, it is unspecified whether fildes can subsequently be passed to any function except close() without error. (not part of the interpretation) The working group noted that there are similar problems in the case that close() returns EIO. Action: ALL to investigate implementation behavior for this case. We may reopen this defect next time, the default will be to leave it as is. Bug 0000527: du and files found via multiple command line arguments Accepted as Marked http://austingroupbugs.net/view.php?id=527 This item is tagged for TC2-2008. An interpretation is required. Interpretation response The standard states that files with multiple links shall be counted and written for only one entry , and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: Existing practice is varied in how du counts files. Notes to the Editor (not part of this interpretation): Change line 84170 [du DESCRIPTION] from: Files with multiple links shall be counted and written for only one entry. to: A file that occurs multiple times under one file operand and that has a link count greater than 1 shall be counted and written for only one entry. It is implementation-defined whether a file that has a link count no greater than 1 is counted and written just once, or is counted and written for each occurrence. It is implementation-defined whether a file that occurs under one file operand is counted for other file operands. In FUTURE DIRECTIONS, change line 84274 from "None" to "A future version of this standard may require that a file that occurs multiple times shall be counted and written for only one entry, even if the occurrences are under different file operands." Change line 84177 [du OPTIONS] from: Regardless of the presence of the -a option, non-directories given as file operands shall always be listed. to: The -a option does not affect whether non-directories given as file operands are listed. Bug 0000528: Support extended regular expressions (EREs) in sed Accepted as Marked http://austingroupbugs.net/view.php?id=528 This item is tagged for Issue 8 Make the changes suggested in the Desired Action and also change: sed [−n] on all three lines of the SYNOPSIS section (P3153, L104762-104764) to: sed [-En] Bug 0000538: Missing part of basename changes from bug 192 Accepted http://austingroupbugs.net/view.php?id=538 Next Steps ---------- The next call is on February 9 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.freenode.org/austingroupbugs 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