Austin Group Minutes of the 10 Apr Teleconference Austin-166 Page 1 of 1 Submitted by Andrew Josey, The Open Group. April 11, 2003 Attendees Andrew Josey, The Open Group Don Cragun , Sun, PASC OR Ulrich Drepper Joanna Farley, Sun Apologies Mark Brown, IBM, TOG OR The call picked up at the aardvark at http://www.opengroup.org/austin/aardvark/finaltext/ XSH --- XSH ERN 15 Response from SSWG-RT: Add the number 10 in the requirements column for all 5 ADV names in the table on lines 12861-12865. After line 12893, add: 10. If path or fildes does not refer to a regular file, it is implementation defined whether an implementation supports an association of the variable name with the specified file. If an implementation supports such an association for other than a regular file, the value returned is implementation defined. Note that it was the intention of .1d that these variables only apply to regular files, but the above requirement allows that an implementation may choose to implement the advisory semantics on other file types unique to that implementation (e.g. a character special device.) Frank Leave open for one final review XSH ERN 65 Alexander supplied additional items. Accept as marked (some debate whether its suitable for TC2) XSH ERN 72 Should the behavior be left unspecified? Left open for further investigation XSH ERN 73, Accept as marked Change "to a maximum of 5 levels deep" to "using a maximum of 5 file descriptors". Global change of the argument "depth" in the parameter list (and text) to fd_limit , and in the example on line 26953 Rationale:"depth" is confusing XSH ERN 74 Accept XSH ERN 75 Accept XBD ----- XBD ERN 15 , the response from the action was that Yes, we need a similar change for sockaddr_in6: The sin6_port and sin6_addr members shall be in network byte order. sin6_family and sin6_scope_id are host byte order. The exact usage of sin6_flowinfo has not been defined, so we really can't make a statement about that in either direction. Leave OPEN for one final review. XBD ERN 19 Some more time needed to consider XCU --- Further time is needed on XCU ERN 5 XCU ERN 6 , reject, it is not a requirement but allows implementations to support it XCU ERN 7 Accept XCU ERN 8 Accept as marked, remove the ctime keyword Next meeting ------------ The next meeting is proposed to be April 24 at the regular timeslot, picking up at XSH before looping back to XBD. Andrew will refill the aardvark hopper prior to the next meeting. Andrew will update the aardvark reports on the web site with the latest information including new aardvark subsequently received.