Minutes of the 11 February 2010 Teleconference     Austin-475 Page 1 of 1
Submitted by Andrew Josey, The Open Group.             February 12 , 2010

Attendees
Andrew Josey, The Open Group
Don Cragun,  PASC OR
Mark Brown, IBM, TOG OR 
Ulrich Drepper, Red Hat
Nick Stoughton, USENIX, ISO/IEC OR
Geoff Clare, The Open Group


Andrew reported that he was ready to circulate bugs 173,185,187 and 188
as proposed interpretations for 30 day review.

Andrew also reported that he would be doing a minor refresh of the
html on February 12 to sweep up known formatting issues reported to date.
(This would include bugs 180 and 183 that he had actions from at the
last meeting)

Don queried whether we had any news from IEEE on the version numbers
for the standard. Andrew replied that we had received no further updates
on the subject.

We picked up on the current bugs

Bug #205 Shell pipeline connection requirement too vague
http://austingroupbugs.net/view.php?id=205 Accepted as Marked
Change

    "The standard output of all but the last command shall be
    connected to the standard input of the next command."

to

    "For each command but the last, the shell shall connect the
    standard output of the command to the standard input of the
    next command as if by creating a pipe and passing the write end of
    the pipe as the standard output of the command and the read
    end of the pipe as the standard input of the next command."

(note the group felt this does not need an interpretation)

Bug #206 fsblkcnt_t and fsfilcnt_t incorrectly marked XSI
http://austingroupbugs.net/view.php?id=210 Accepted as marked
Make the suggested change and also remove XSI shading from where these type
names are used on line 13417.
(note the group felt this does not need an interpretation)

Bug #213 Definition of pututxline() is slightly too restrictive to allow
flexible implementations
http://austingroupbugs.net/view.php?id=213 Accepted as marked
We considered this during the 2010-01-21 conference call.
We agree with Note: 0000375 and plan to address that issue by adding ut_line
before ut_pid on line 25429.

We are concerned that the main change proposed for this issue would have
observable effects on existing applications, and may lead to breaking such
applications.

We are willing to remove the absolute requirement to implement pututxline with
getutxid, but not to go as far as suggested. 
Proposed new wording:

  If the process has appropriate privileges, the pututxline( ) function
  shall write out the structure into the user accounting database. It
  shall search for a record as if by getutxid() that satisfies the
  request. If this search succeeds, then the entry shall be replaced.
  Otherwise, a new entry shall be made at the end of the user accounting
  database.

Bug #215 Inconsistencies in pwrite() and write() errors 
http://austingroupbugs.net/view.php?id=215 Accepted
This should go down the interpretations track:

Interpretation response
------------------------
The standard states the current pwrite() and write() error conditions , and
conforming implementations must conform to this. However, concerns have been
raised about this which are being referred to the sponsor.


Notes to the Editor (not part of this interpretation):
-------------------------------------------------------
Make change suggested by Submitter.


Bug #216 Control characters must have single-byte encodings
http://austingroupbugs.net/view.php?id=216 OPEN
This bug was discussed at some length but no consensus reached as yet.



Next Steps
----------
The next call will be on March 4th at 16:00 UK time/08:00 Pacific
to carry on with the defect reports

http://austingroupbugs.net


See the calendar for the list of dialup numbers.

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