Minutes of the 2 June 2011 Teleconference Austin-524 Page 1 of 1 Submitted by Andrew Josey, The Open Group. June 3 , 2011 Attendees Andrew Josey, The Open Group Don Cragun, PASC OR Jim Pugsley, Oracle Geoff Clare, The Open Group Mark Brown, IBM, TOG OR Eric Blake, Red Hat Nick Stoughton, USENIX, ISO/IEC OR * Old Business Geoff had reopened bug #397 Bug 397 0000397: setbuf and errno Accepted as Marked http://austingroupbugs.net/view.php?id=397 This item is tagged for TC1-2008 Since existing implementations do not work to preserve errno values in the case of no error, the following changes should be made instead: At p 1855 line 59282, change ERRORS text from: No errors are defined. To: Although the setvbuf() interface may set errno in defined ways, the value of errno after a call to setbuf() is unspecified. At line 59289 add to Application Usage: Since errno is not required to be unchanged on success, in order to correctly detect and possibly recover from errors, applications should use setvbuf() instead of setbuf(). * New Business We picked up on Bug processing for bugs reported against project Issue 7. Bug 0000411: adding atomic FD_CLOEXEC support OPEN http://austingroupbugs.net/view.php?id=411 Eric still has an open action to complete the changes for popen(). Bug 0000416: Message description for "val" is inconststent OPEN http://austingroupbugs.net/view.php?id=416 Jim has an action to research the behaviour of the val utility, including the correct format strings for STDOUT to match historic practice Bug 0000417: ${#?} is ambiguous Accepted as Marked http://austingroupbugs.net/view.php?id=417 This item is tagged for TC1-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 expansion ${#?} can be interpreted both as the length of $? and as $# giving an error in the (impossible) case that it is not set. Notes to the Editor (not part of this interpretation): At line 72734 insert a sentence before "The following table summarizes ...": If parameter is '#' and the colon is omitted, the application shall ensure that word is specified (this is necessary to avoid ambiguity with the string length expansion). Bug 0000418: posix_spawn_file_actions_addclose() should not check against OPEN_MAX Accepted http://austingroupbugs.net/view.php?id=418 This item is tagged for TC1-2008. An interpretation is required. Interpretation response: The standard states that posix_spawn_file_actions_addclose must fail if the argument exceeds OPEN_MAX, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: See Description. Notes to the Editor (not part of this interpretation): See Desired Action. Bug 0000419: ambiguity in close() EBADF Accepted http://austingroupbugs.net/view.php?id=419 This item is tagged for TC1-2008. Bug 0000420: rationale for filename talks about characters, but filenames consist of bytes Accepted http://austingroupbugs.net/view.php?id=420 This item is tagged for TC1-2008. Bug 0000421: Inconsistent casting of -1 in RETURN VALUE sections Accepted http://austingroupbugs.net/view.php?id=421 This item is tagged for TC1-2008. Bug 0000422: list of functions that can modify the state of a directory stream file description is incomplete Accepted http://austingroupbugs.net/view.php?id=422 This item is tagged for TC1-2008. Next Steps ---------- The next call will be on June 9th 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. As we have a number of open defects we will investigate holding additional meetings. Andrew will setup a poll to identify timeslots. 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