Minutes of the 9 June 2011 Teleconference Austin-525 Page 1 of 1 Submitted by Andrew Josey, The Open Group. June 10 , 2011 Attendees Andrew Josey, The Open Group Don Cragun, PASC OR Geoff Clare, The Open Group Mark Brown, IBM, TOG OR Nick Stoughton, USENIX, ISO/IEC OR Apologies Eric Blake, Red Hat Jim Pugsley, Oracle Andrew has added some additional meetings based on a poll of the core participants. These are in the Austin Group calendar. http://www.opengroup.org/platform/single_unix_specification/events.tpl * Old Business Left open from last time 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 * New Business We picked up on Bug processing for bugs reported against project Issue 7. Bug 0000391: ENOTSUP should not be a valid error for dirfd() Future Enhancement http://austingroupbugs.net/view.php?id=391 Don had completed his action. It was agreed that this item ought to be targeted for Issue 8. This item is tagged for Issue 8. Bug 0000415: add SEEK_HOLE, SEEK_DATA to lseek Future Enhancement http://austingroupbugs.net/view.php?id=415 This item is tagged for Issue 8. Bug 0000423: ls -m output format is not clear Accepted http://austingroupbugs.net/view.php?id=423 Don had completed an action from last time and updated the bug. 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: See Description. Notes to the Editor (not part of this interpretation): See "Desired Action" Bug 0000424: The list of mutually exclusive ls utility options is missing some entries. Future Enhancement http://austingroupbugs.net/view.php?id=424 This item is tagged for Issue 8. Bug 0000426: The description of the block size used by ls -s when -k is not also given is inconsistent. Withdrawn by submitter http://austingroupbugs.net/view.php?id=426 Bug 0000444: restrict missing from getsubopt Accepted http://austingroupbugs.net/view.php?id=444 This item is tagged for Issue 8 Bug 0000446: incorrect variable type in example code Accepted as marked http://austingroupbugs.net/view.php?id=446 This item is tagged for TC1-2008 In addition to the change in the Desired Action, also change: const char* b to: const unsigned char* b on line 81170 and change: c = (unsigned)(*b++); to: c = *b++; on line 81175. Bug 0000445: Rationale of find -exec + refers to incompatibilities with C standard Accepted as Marked http://austingroupbugs.net/view.php?id=445 This item is tagged for TC1-2008 Replace It should be noted that this is an incompatible change to the ISO/IEC 9899: 1999 standard. For example, the following command prints all files with a ’−’ after their name if they are regular files, and a ’+’ otherwise: with It should be noted that this is an incompatible change to the 1003.2-1992 standard. For example, the following command printed all files with a ’−’ after their name if they are regular files, and a ’+’ otherwise: Bug 0000447: strerror_r and strerror_l error checking Accepted as Marked http://austingroupbugs.net/view.php?id=447 This item is tagged for TC1-2008 An interpretation is required. Interpretation response: The standard does not speak to this issue, and as such no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale: See description. Notes to the Editor (not part of this interpretation): At line 63244 [XSH strerror DESCRIPTION], change: The strerror( ) and strerror_l( ) functions shall not change the setting of errno if successful. Since no return value is reserved to indicate an error, an application wishing to check for error situations should set errno to 0, then call strerror( ), then check errno. to: The strerror( ) and strerror_l( ) functions shall not change the setting of errno if successful. Since no return value is reserved to indicate an error of strerror( ), an application wishing to check for error situations should set errno to 0, then call strerror( ), then check errno. Similarly, since strerror_l( ) is required to return a string for some errors, an application wishing to check for all error situations should set errno to 0, then call strerror_l( ), then check errno. (note : The interpretation response above does not include the changes strerror_r suggested by the submitter. The change proposed here is suitable for TC1, but strerror_r should wait for the next revision. A separate bug should be filed if that is desired.) Bug 0000450: fsetpos() ESPIPE for sockets Accepted http://austingroupbugs.net/view.php?id=450 An interpretation is required. Interpretation response: The standard does not speak to this issue, and as such no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale: The change described in the change history was applied in Draft 3 (Feb 29 2000), but then changed inn D5 (December 15 2000). It is not clear that the removal was intentional or part of a ballot comment. Notes to the Editor (not part of this interpretation): See Desired Action Bug 0000451: PATH_MAX and getpid() problems in fprintf() example Accepted http://austingroupbugs.net/view.php?id=451 This item is tagged for TC1-2008 Bug 0000453: strtol() EINVAL problems Accepted http://austingroupbugs.net/view.php?id=453 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 DESCRIPTION section says an error may occur, but the ERRORS section does not describe the error that may occur. Notes to the Editor (not part of this interpretation): Make the changes suggested in the Desired Action. Next Steps ---------- The next call is an extra call on June 15th at 07:30 Pacific for one hour only and will continue processing defect reports. The next call after that will be on June 16th 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