Minutes of the 3rd October 2019 Teleconference     Austin-973 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 4th October 2019

Attendees:
    Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
    Andrew Josey, The Open Group
    Don Cragun, IEEE PASC OR
    Geoff Clare, The Open Group
    Joerg Schilling, FOKUS Fraunhofer
    Eric Blake, Red Hat, Open Group OR
    Mark Ziegast, SHware Systems Dev.

* General news 
None.

* Outstanding actions

(Please note that this section has been flushed to shorten the minutes -
to locate the previous set of outstanding actions, look to the minutes
from 13th June 2019 and earlier)

Bug 1254: "asynchronous list" description uses "command" instead of "AND-OR list" OPEN
http://austingroupbugs.net/view.php?id=1254
Action: Joerg to investigate how his shell behaves.

Bug 700 - Nick to raise this issue with the C committee
Bug 713 - Nick to raise with the C committee.
Bug 739 - Nick to raise with the C committee.
Bug 1216 - Eric to ask if The Open Group is willing to sponsor this interface, referencing bug note 4478.


* Current Business


Bug 789: Add set -o pipefail  Accepted as Marked
http://austingroupbugs.net/view.php?id=789

This item is tagged for Issue 8.

On 2016 edition page 2369 line 75648 section 2.9.2, change:
    If the pipeline does not begin with the ! reserved word, the
    exit status shall be the exit status of the last command specified
    in the pipeline. Otherwise, the exit status shall be the logical
    NOT of the exit status of the last command. That is, if the
    last command returns zero, the exit status shall be 1; if the
    last command returns greater than zero, the exit status shall
    be zero.

to:
    The exit status of a pipeline shall depend on whether or not
    the pipefail option (see [xref to set]) is enabled and whether
    or not the pipeline begins with the ! reserved word, as described
    in the following table. The pipefail option determines which
    command in the pipeline the exit status is derived from; the !
    reserved word causes the exit status to be the logical NOT of
    the exit status of that command. The shell shall use the pipefail
    setting at the time it begins execution of the pipeline, not
    the setting at the time it sets the exit status of the pipeline.
    (For example, in <tt>command1 | set -o pipefail</tt> the exit
    status of <tt>command1</tt> has no effect on the exit status
    of the pipeline, even if the shell executes<tt>set -o pipefail</tt>
    in the current shell environment.)

      pipefail Enabled    Begins with !      Exit Status

        no                  no             The exit status of the last (rightmost)
                                           command specified in the pipeline.

        no                  yes            Zero, if the last (rightmost) command
                                           in the pipeline returned a non-zero
                                           exit status; otherwise, 1.

        yes                 no             Zero, if all commands in the pipeline
                                           returned an exit status of 0;
                                           otherwise, the exit status of the
                                           last (rightmost) command specified in
                                           the pipeline that returned a non-zero
                                           exit status.

        yes                 yes            Zero, if any command in the
                                           pipeline returned a non-zero
                                           exit status; otherwise, 1.

On 2016 edition page 2411 line 77180 section set, add after nounset:
    pipefail
	Derive the exit status of a pipeline from the exit statuses
	of all of the commands in the pipeline, not just the last
	(rightmost) command, as described in [xref to 2.9.2].

1283: should chmod() ignore file type bits in st_mode       Accepted as Marked
http://www.austingroupbugs.net/view.php?id=1283

This item is tagged for TC3-2008.

An interpretation is required.

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.

Rationale:
The selected option matches current existing practice, but alternative implementations have been investigated.

Notes to the Editor (not part of this interpretation):
Implement OPTION 1 from the Desired Action, but change:

    the st_mode value returned by stat() but cannot

to:

    the st_mode value returned by lstat() or stat() but cannot




Next Steps 
----------
The next calls are on:

October 7 2019 (Monday)
This call will be for 60 minutes.

October 10 2019 (Thursday)
This call will be for 90 minutes.

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

Please check the calendar invites for dial in details.
http://austingroupbugs.net

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

https://posix.rhansen.org/p/201x-mm-dd
username=posix password=2115756#