Minutes of the 23 July 2015 Teleconference     Austin-722 Page 1 of 1
Submitted by Andrew Josey, The Open Group.  24th July 2015

Attendees:
    Mark Ziegast, SHware Systems
    Don Cragun, IEEE PASC OR
    Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
    Geoff Clare, The Open Group
    Joerg Schilling, FOKUS Fraunhofer
    Martin Rehak, Oracle
    Jim Grisanzio, Oracle
    David Clissold, IBM (apologies, delayed, joining ~0:53)
    Eric Blake, Red Hat
    Richard Hansen, BBN

Apologies:
    Andrew Josey

* General news

None.


* Outstanding actions

( Please note that I have flushed this section to shorten the minutes -
to locate the last set of outstanding actions, look
to the minutes from 26 Feb 2015)

Bug 0000887: printf and other functions appear many times in search results OPEN
http://austingroupbugs.net/view.php?id=887
Andrew is investigating.

Bug 0000900: add qsort_r        OPEN
http://austingroupbugs.net/view.php?id=900

The consensus was that its a good idea to add the suggested interface.
The usual requirements regarding a sponsor for a new interface
apply.

Action: Open Group OR , to ask the Base WG if they wish to sponsor
the additional qsort interface proposed here.

Bug  0000901: reserve _POSIX* shell option namespace for future use        OPEN
http://austingroupbugs.net/view.php?id=901

The forward plan for this bug remains as before:

    Richard: file a new bug report with a concrete feature that
    would use the _POSIX* namespace (as motivation for reserving
    set -o _POSIX*)

    All: debate the proposed feature.  If it's something we want,
    then revisit bug #901.  If not, close bug #901.



Bug 0000922: Implementations should be allowed to change/remove implementation-defined environment variables         OPEN
http://austingroupbugs.net/view.php?id=922

This item remains open. 

Action on Eric: propose wording for Issue 8 to add secure_getenv(),
and make it clear that deleting from environment without explicit
request is not compliant, but ignoring is fine.

For Issue 7 TC 2: Create new bug to add additional conditions on
what makes TMPDIR valid, vs. undefined behavior; also add future
directions to getenv() to mention secure_getenv()


Bug #960: export can fail        OPEN
http://austingroupbugs.net/view.php?id=960

Action: Eric to incorporate Geoff's comments, add wording for 'exit'
and 'return'

* Current Business

Bug #971: join -t separator underspecified, example incorrect Accepted as Marked
http://austingroupbugs.net/view.php?id=971

This item is tagged for TC2-2008

Change P2841, L93392 from:

    would produce:
to:
    (where <tt><tab></tt> is a literal <tab> character) would produce:


Bug #970: mkstemp() description permits mode 0640 or 0620, should only permit 0600        Accepted as Marked
http://austingroupbugs.net/view.php?id=970

An interpretation is required.

Interpretation response:
The standard states the requirements for the m4 mkstemp function,
and conforming implementations must conform to this. However,
concerns have been raised about this which are being referred to
the sponsor.

Rationale:
The current standard does not match any existing practice. The m4
utility uses the mkstemp() function and does not modify the umask
nor call chmod() after creating the file.

Notes to the Editor (not part of this interpretation):
On page 2902 lines 95766-95777, change:
    The first argument shall be taken as a template for creating
    an empty file, with trailing <tt>'X'</tt> characters replaced
    with characters from the portable filename character set. The
    behavior is unspecified if the first argument does not end in
    at least six <tt>'X'</tt> characters. If a temporary file is
    successfully created, then the defining text of the macro shall
    be the name of the new file. The user ID of the file shall be
    set to the effective user ID of the process. The group ID of
    the file shall be set to the group ID of the file's parent
    directory or to the effective group ID of the process. The file
    access permission bits are set such that only the owner can
    both read and write the file, regardless of the current umask
    of the process.

to:
    The defining text shall be as if it were the resulting pathname
    after a call to the mkstemp() function defined in the System
    Interfaces volume of POSIX.1-2008 called with the first argument
    to the macro invocation, followed by closing that file.



Bug #966: Atomicity requirements for read/write ambiguity Accepted as Marked
http://austingroupbugs.net/view.php?id=966


This item is tagged for TC2-2008

On page 2291 line 72619, change from:

This volume of POSIX.1-2008 does not specify behavior of concurrent
writes to a file from multiple processes.

to:

This volume of POSIX.1-2008 does not specify the behavior of
concurrent writes to a regular file from multiple threads, except
that each write is atomic (see [xref to 2.9.7]).



Next Steps
----------
The next call is on July 30, 2015 (a Thursday)
Apologies in Advance:
     A. Josey, 30th

Calls are anchored on US time. (8am Pacific) 

This call will be for the regular 90 minutes.

http://austingroupbugs.net

An IRC channel will be available for the meeting
irc://irc.freenode.net/austingroupbugs

An etherpad is usually up for the meeting, with a URL using the date format as below:

http://posix@posix.rhansen.org:9001/p/201x-mm-dd
password=2115756#