Austin Group Minutes of the 12 August Teleconference Austin-218 Page 1 of 1
Submitted by Andrew Josey, The Open Group. August 13, 2004
Attendees
Andrew Josey, The Open Group
Don Cragun , Sun, PASC OR
Ulrich Drepper, Red Hat
Nick Stoughton, USENIX, WG15 OR
Joanna Farley, Sun
Apologies
Mark Brown, IBM, TOG OR
Dave Butenhof, HP
Draft Status
---------------
ANSI has submitted the final draft TC2 to ISO.
Defect Report Processing
-------------------------
The group picked up on the latest batch of defect reports,
which are available at the following URL:
http://www.opengroup.org/austin/aardvark/latest/
XSH ERN 39 pthread_mutex_setprioceiling() possibility of having a
deadlock, if the call is made with the mutex already locked. Accept as
marked below.
The standard is unclear on this issue, and no conformance
distinction can be made between alternative implementations based
on this. This is being referred to the sponsor for addressing
in a future revision.
(add to SD/5)
XSH ERN 41 exit should not invoke cancellation cleanup handlers or
per-thread data destructors. Accept as marked below.
It is agreed that this is a defect, that exit() should not invoke
cancellation cleanup handlers or per-thread data destructors.
Concerns are being forwarded to the sponsor.
Instructions for the editor for a future revision:
exit() should be described on a separate page that explains at the end
that exit() inherits the behavior described separately for _exit()
XSH ERN 42 sigpause, process signal mask, use in threaded apps Accept
as marked below
It is agreed that this is a defect, that there are inconsistencies
in the standard related to use of sigpause in threaded applications.
Concerns are being forwarded to the sponsor.
Considerations for a future revision:
In the next revision we should either deprecate sigpause and
related functions or define them to be thread-safe.
This rdvk should be copied to SD/5.
XSH ERN 44 pthread_cond_timedwait EINVAL Error should be
described consistently with other interfaces Accept
For the error EINVAL,
change: "The value specified by abstime is invalid."
with: "The abstime argument specified a nanosecond value less than
zero or greater than or equal to 1000 million."
XSH ERN 46 new function proposed tremove Accept as marked below
Alternative 1 of modifying existing behavior is not acceptable. Alternative 2
proposing a new function is acceptable for consideration
in the next revision, full text would be helpful.
Copy this rdvk into SD/5.
XSH ERN 47 missing function res_init() Reject
It was agreed that this is a problem for applications, but that
it is not possible to specify the function in a general
enough way (without going into system details beyond the
scope of the standard) for inclusion in the standard.
XSH ERN 48 errors for readdir() apply to readdir_r() Accept
XSH ERN 49 applications must specify one of the flags WEXITED , WSTOPPED,
or WCONTINUED with waitid(). Accept as marked below
Replace line 50190f with
The options argument is used to specify which state changes waitid()
shall wait for. It is formed by OR ing together the following flags:
Add after line 50199:
The results are unspecified if at least one of the flags WEXITED ,
WSTOPPED, or WCONTINUED is not specified in the /options/ argument.
[note to readers, open() states along the lines of:
Applications shall specify at least one of the flags WEXITED,
WSTOPPED or WCONTINUED in the /options/ argument .]
XSH ERN 50 pthread_cond_wait with a recursive mutex that is locked several time. Accept as marked below
The standard does not speak to this issue, and as such no conformance
distinction can be made between alternative implementations based on this.
This permits implementations to choose how to handle situations where an
application might deadlock, some implementations might choose to detect
and report that deadlock while others wouldn't.
XCU ERN 35 does "sort -o -" create a file named "-" Accept as marked below
In the example given
sort -o -
the final "-" is an option argument; not an operand. The description
of the -o option says that the output option argument is the name of
an output file to be used instead of standard output, so a file
named "-" shall be created. No change is necessary to the standard.
Notes to working group
A related issue was raised on Utility Syntax Guideline 13
and general applicability to other utilities.
For the current standard, the standard is unclear. This
means thatportable applications can *only*
depend on one or other of the behaviors (i.e. - is stdin,
stdout or a filename) if the standard explicitly describes it.
In the next revision we need to clarify guideline 13
and explicitly state that for any utility that handles filename
operands how "-" should be treated.
Possible words for a future revision
At Page XBD 204, line 7233, replace
"Guideline 13: For utilities that use operands to represent files to be
opened for either reading or writing, the - operand should be used only
to mean standard input (or standard output when it is clear from context
that an output file is being specified)."
with
"Guideline 13: For utilities that use operands to represent files to be
opened for either reading or writing, the - operand should be used to
mean only standard input (or standard output when it is clear from
context that an output file is being specified) or a file named -."
After line 7240, add
"Where a utility described in the Shell and Utilities volume of IEEE Std
1003.1-2001 as conforming to these guidelines accepts the operand - to
mean standard input or output, this usage shall be explained in the
OPERANDS section."
Next Steps
-----------
Andrew will update the aardvark reports with the latest inbound
defect reports.
There are a number of open action items outstanding:
1. Don Cragun Pathname Resolution proposal
2. Larry Dwyer system() and threads
3. Joerg Schilling wording for XCU ERN 1 pax
The next teleconference call is scheduled for August 19 2004