Austin Group Minutes of the 11 May Teleconference Austin-297 Page 1 of 1 Submitted by Andrew Josey, The Open Group. May 12, 2006 Attendees Andrew Josey, The Open Group Nick Stoughton, USENIX, ISO/IEC OR Don Cragun , Sun, PASC OR Apologies: Mark Brown, IBM, TOG OR Ulrich Drepper, Red Hat Action item review --------------------- ACTION AI-2006-02-04: Nick Stoughton to submit an aardvark against link() when the appropriate time is reached w.r.t. approval of strawman 2. STATUS: OPEN ACTION AI-2006-02-08: Andrew Josey to submit an aardvark against at, batch and crontab to make the directory used for the allow and deny files implementation defined. STATUS: CLOSED ACTION AI-2006-02-28: AJ to filter the XSH, XCU and XRAT aardvarks for SD5 and interps material. STATUS: OPEN, ongoing in progress Austin/280r1 is the latest notes arising from SD5,Andrew has now completed this. Some issues were raised on items in there. ACTION AI-2006-04-01: Nick Stoughton/Andrew Josey to send reports to SC22 prior to the Sep 2006 SC22 Plenary (due date: July 2006) STATUS: OPEN ACTION AI=2006-05-01: All, Review the PASC draft PAR http://www.opengroup.org/austin/docs/austin_296.pdf PASC Status ----------- Andrew noted that he has produced the first draft of the PASC PAR as Austin/296. We need everyone to review this. The PASC PMC criteria still have to be created. http://www.opengroup.org/austin/docs/austin_296.pdf Issues with Austin 280r1 (notes arising from SD5) ------------------------------------------------- http://www.opengroup.org/austin/docs/austin_280r1.txt SD5 XBD ERN 4 An issue has been raised with this part of the proposed change: |On XSH page 350 fdopen | |Delete 11491 in the ERRORS section: | |11491 [EMFILE] {STREAM_MAX} streams are currently open in the calling process. | |STREAM_MAX is required to be the same value as FOPEN_MAX |and so we do not need the separate error case. | |Errors that reference FOPEN_MAX or STREAM_MAX should coalesced |to be | | [EMFILE] {FOPEN_MAX} (and {STREAM_MAX} if defined) streams ... "I don't think that's right. Although the constant STREAM_MAX in limits.h must, if defined, have the same value as FOPEN_MAX (the constant in stdio.h), the notation {STREAM_MAX} in the EMFILE text refers to the limit value obtained from sysconf(_SC_STREAM_MAX), which can be different from FOPEN_MAX. It would be less confusing if the braces were omitted from {FOPEN_MAX}. (I think the braces should really only be used when referring to a limit value obtainable from sysconf() or pathconf(), and not when referring to constants defined in headers. Unfortunately there are several places where the braces are also used for constants.) Also, since the actual {STREAM_MAX} limit can be queried at runtime, I think the EMFILE errors for exceeding {STREAM_MAX} should probably be "shall fail" errors, not "may fail" errors. (The FOPEN_MAX EMFILE errors need to stay as "may fail".) " It was agreed that we should undo the proposed change and omit that from Austin 280r1. On the point whether the error cases should be shall fail vs may fail, it was felt that we could not look to make this change on the strength of this message alone and it would require another aardvark and be considered separately. SD5 XSH ERN 120 An comment had been raised on the proposed APPLICATION USAGE for sched_yield. It was agreed to leave this open until next time. Andrew will mark the matter in Austin 280r1 as OPEN Defect Report Processing ------------------------- We picked up on recent aardvarks http://www.opengroup.org/austin/aardvark/latest/ XSH ERN 127 getnameinfo http://www.opengroup.org/austin/mailarchives/ag/msg09425.html (mail seq Austin 9427) It was agreed to go along with Jack Mccann's suggestion Change from Note: The IPv6 unspecified address (::) and the IPv6 loopback address (::1) are not IPv4-compatible addresses. If the address is the IPv6 unspecified address (::), a lookup is not performed, and the EAI_NONAME error is returned. To: (regular normative text) If the address is the IPv6 unspecified address (::), a lookup shall not be performed and the behavior shall be the same as when the node's name cannot be located. Add to Application Usage The IPv6 unspecified address (::) and the IPv6 loopback address (::1) are not IPv4-compatible addresses. Remove "under all circumstances" in both places on the getnameinfo() page since its superfluous. XBD ERN 67 SCHAR_MIN limits.h/stdint.h Accept as marked below We reviewed the mail discussions on the reflector. The proposed change was amended as follows: Change the stdint.h RATIONALE, XBD page 323 lines 11533-11536 from 11533 As a consequence of adding int8_t, the following are true: 11534 "A byte is exactly 8 bits. 11535 "{CHAR_BIT} has the value 8, {SCHAR_MAX} has the value 127, {SCHAR_MIN} has the 11536 value -127 or -128, and {UCHAR_MAX} has the value 255. to As a consequence of adding int8_t, the following are true: "A byte is exactly 8 bits. "{CHAR_BIT} has the value 8, {SCHAR_MAX} has the 127, {SCHAR_MIN} has the value -128, and {UCHAR_MAX} has the value 255 (The POSIX standard explicitly requires 8 bit characters and two's complement arithmetic.) Left open from the previous meeting to address next time: XCU ERN 22/23 awk OPEN XCU ERN 57 mv OPEN Next Steps ----------- Andrew will update the aardvark reports with the latest inbound defect reports. The next call will be 18th May 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