Austin Group Minutes of the 23 October Teleconference Austin-196 Page 1 of 1
Submitted by Andrew Josey, The Open Group.              October 24, 2003

Attendees

Andrew Josey, The Open Group
Don Cragun , Sun, PASC OR
Joanna Farley, Sun 
Mark Brown, IBM, TOG OR 
Ulrich Drepper, Red Hat
Nick Stoughton, USENIX, WG15 OR
Dave Butenhof, HP

Draft Status

The IEEE ballot and The Open Group company review are in progress.
So far 19 bugs have been received (18 in aardvark , 1 to be fed
to the aardvark).

Aardvark

We picked up at the new inbound aardvark at
http://www.opengroup.org/austin/aardvark/finaltext-post-tc2/


XCU ERN 1

Standard is clear, standard is wrong, allow either behavior
until the next revision
Still need proposed wording.
Leave open for one more week

XSH ERN 6

A/M

Add to the end of the DESCRIPTION
"If the struct aiocb pointed to by aiocbp is not associated
with an operation that has been scheduled the results are undefined."
                                                                                


XBD ERN 2 
Reject
arpa/inet.h is allowed to make netinet/in.h visible, and netinet/in.h
is allowed to make sys/socket.h visible.

XCU ERN 4 Accept
XCU ERN 5 Accept (possible errata item?)
XCU ERN 6 Accept (possible errata item?)
XCU ERN 7 Accept (possible errata item?)
XCU ERN 8 Accept
XCU ERN 9 Accept

Andrew will feed the aardvark,looking ahead

XSH ERN 12
(access from gwc)
Reject, the first para already requires this, and in all
cases its the process that has privileges not the id.

XSH ERN 13
fgetc (from carol) Accept

XSH ERN 15
fgets (from carol) Accept

XSH ERN 18
pthread_barrier_wait 
(13:34) reject first one would make it difficult to implement

XSH ERN 19
with condition variables and mutexes etc 
(19:01) reject, we did not see the need for the clarifying text

XSH ERN 20
pthread_mutex_setprioceiling (mgh)
A/M
Add a may fail EDEADLK to the beginning

XSH ERN 11
pthread_mutexattr_setprotocol (mgh)
Reject.  This would be a significant change on requirements on systems.
                                                                                
The feeling of the review group was that if an application wants round
robin behavior it should request round robin (RR) scheduling , and
that if an application specified RR you should assume it requested it.
If an application needs FIFO it should request it.
An alternate statement of this would be to say that
SCHED_RR threads get changed to SCHED_FIFO when locked on a mutex that
has been initialized with prio inherit or prioprotect



Next Steps
-----------

Andrew has updated the rdvk.
The next meetin is November 6th