Austin Group Minutes of the 3rd August Teleconference Austin-309 Page 1 of 1 Submitted by Andrew Josey, The Open Group. August 4, 2006 Attendees Andrew Josey, The Open Group Nick Stoughton, USENIX, ISO/IEC OR Don Cragun , Sun, PASC OR Ulrich Drepper, Red Hat Mats Wichmann Apologies Mark Brown, IBM, TOG OR 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-28: AJ to filter the XSH, XCU and XRAT aardvarks for SD5 and interps material. (ongoing action) STATUS: OPEN, ongoing in progress The cutoff for draft 1 was June 12. We are not planning to take any changes past that date at the moment. Austin/280r1 is the latest notes arising from SD5 and is frozen The new document with new issues arising from SD5 is Austin/302 Action AI-2006-06-01: Andrew to work out the full set of changes for recirculation for XSH ERN 132 OPEN Next Face to Face meeting ---------------------------- Andrew reported that he sent out the Logistics information to the reflector. PASC PAR status ----------------- Andrew had received a request for clarifications on the scope, and purpose. He had responded and needs to fold the updates into the draft long scope and the next draft of the document. Aardvark Defect report processing: ----------------------------------- OPEN ERNS carried forward: XBD ERN 68 XBD limits.h tracing limits OPEN Fwded to SSWG-RT (Andrew has completed the action) Andrew had also sent email to Joe Gwinn requesting help from the SSWG-RT but is yet to get a response. XSH ERN 132 %M for fscanf OPEN This is invention, but arises from the LSB conflicts. Leave open, need to work on the wording, including fwscanf specifics before we can move forward Action 2006-06-01: Andrew to work out the full set of changes for recirculation for XSH ERN 132 OPEN XSH ERN 133 open and implementation added flags OPEN Left open since we need specific wording XSH ERN 162 OPEN We need some expert input from realtime experts on this item. At the moment silence should be read as unspecified. --- +The above carried forward OPEN from last time, we picked up as follows: XSH ERN 156 pipe Accept as marked. This was reopened at Don's request and the closed as accept as marked as follows: Insert before line 28279: "The pipe's user ID shall be set to the effective user id of the calling process." "The pipe's group ID shall be set to the effective group id of the calling process." XCU ERN 94 ed SIGHUP/disconnect OPEN This was left OPEN since Mark was not on the call. It was updated with discussions from the reflector It was agreed that we need to make the wording consistent between the terminal disconnect text and SIGHUP, or point from one to the other. ACTION AI-2006-07-01: Mark Brown to take action to supply wording. CLOSED his action as follows: I propose the following ACTION be taken for XCU ERN 94: Replace the text on XCU page 340, lines 13108-13114 with the following: " The ed utility shall operate as if a SIGHUP signal had been detected." Change the text on XCU page 337 line 12986 to read: "shall exit without writing the file to the currently remembered pathname and without returning to command mode." Geoff responded with: If the changes proposed in PASC 1003.2-92 #36 are for some reason not suitable, then I would suggest the following as the replacement for 13108-13114 (the terminal disconnect case): If the terminal disconnect is accompanied by delivery of a SIGHUP signal, the ed utility shall operate as described in the ASYNCHRONOUS EVENTS section for the SIGHUP signal. If a SIGHUP signal is not delivered, the ed utility shall operate as if end-of-file had been detected on standard input. XCU ERN 95 at and absolute directory names Accept as marked Change in the XSI shaded text in DESCRIPTION (at utility page 144 line 5501) (batch utility page 190 line 7433) "the file /usr/lib/cron/at.allow" to "the file at.allow which is located in an implementation-defined directory". Change in the XSI shaded text in DESCRIPTION (crontab utility page 275 line 10741) "the file /usr/lib/cron/cron.allow" to "the file cron.allow which is located in an implementation-defined directory". Change (at utility page 144 line 5502) (batch utility page 190 line 7433) "the file /usr/lib/cron/at.deny shall be checked" to "the file at.deny, which is located in an implementation-defined directory, shall be checked" Change ( crontab utility page 275 line 10742) "the file /usr/lib/cron/cron.deny shall be checked" to "the file cron.deny, which is located in an implementation-defined directory, shall be checked" In INPUT FILES (at utility page 144 line 5697) (batch utility page 190 line 7446) Change "The text files /usr/lib/cron/at.allow and /usr/lib/cron/at.deny shall" to "The text files at.allow and at.deny, which are located in an implementation-defined directory, shall..." In INPUT FILES (crontab utility page 276, line 10787) Change "The text files /usr/lib/cron/cron.allow and /usr/lib/cron/cron.deny shall" to "The text files cron.allow and cron.deny, which are located in an implementation-defined directory, shall..." XCU ERN 96 cmp -l Accept XCU ERN 97 SYNOPSES layout Accept as Marked Mutually exclusive options should have no space before or after pipe symbol. For bracketed groups of options, the bracketed groups should be separated by a space grep is a good example of not looking like it should So grep should be: 19118 grep [−E|−F] [−c|−l|−q] [−insvx] −e pattern_list... 19119 [−f pattern_file]... [file...] 19120 grep [−E|−F] [−c|−l|−q] [−insvx] [−e pattern_list]... 19121 −f pattern_file... [file...] 19122 grep [−E|−F] [−c|−l|−q] [−insvx] pattern_list [file...] This will require a global editorial pass. Action 2006-08-01: AJ to discuss with Cathy and confirm at the meeting how they are to be handling. XCU ERN 98 grep -l and -q Accept XCU ERN 99 m4 max number of diverts Accept Next Steps ----------- Andrew will update the aardvark reports with the latest inbound defect reports. The next call will be 17 August 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