Minutes of the 25 September 2014 Teleconference

[Andrew Josey]

All
Enclosed are the minutes of 25 Sep 2014 teleconference
regards
Andrew
----

Minutes of the 25 September 2014 Teleconference Austin-676 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 26th September 2014

Attendees:
Andrew Josey, The Open Group
Don Cragun, IEEE PASC OR
Eric Blake, Red Hat
Geoff Clare, The Open Group
Richard Hansen, BBN
Martin Rehak, Oracle

Apologies
Matthew Dempsky, OpenBSD
Mark Ziegast, SHware Systems
Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
David Clissold, IBM
Joerg Schilling FOKUS Fraunhofer
Mark Brown, Canonical

* General news

On the PASC PAR approval progress - still open. Don currently has the action to progress.


* Outstanding actions

+Bug 0000251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames OPEN
http://austingroupbugs.net/view.php?id=251
Don has an action to produce a proposal.

+Bug 0000561: NUL-termination of sun_path in Unix sockets OPEN
http://austingroupbugs.net/view.php?id=561
Eric has an action to update the proposal.

+Bug 0000573: Please add '+' to the portable filename character set OPEN
http://austingroupbugs.net/view.php?id=573
Joerg has an action to prepare a proposed change.

+Bug 0000592: consistent use of struct timespec OPEN
http://austingroupbugs.net/view.php?id=592
Jim had provided additional information in bugnote 1627.
This was discussed and Jim took an action to provide further information.

+Bug 0000598: OH shading and new interfaces OPEN
http://austingroupbugs.net/view.php?id=598
Eric has an action to propose a new solution with self-contained headers.

+Bug 0000517: EBNF support OPEN
http://austingroupbugs.net/view.php?id=517
Action on Joerg to look at this.

+Bug 0000633: SIGEV_THREAD delivery renders many signal interfaces unsafe
OPEN
http://austingroupbugs.net/view.php?id=633
We noted that feedback has settled down on the mailing list, and
will discuss next session.

+Bug 0000657: Conditions under which fmemopen() write a NUL to the buffer
are insufficiently specified OPEN
http://austingroupbugs.net/view.php?id=657
Eric has an action to propose wording to clarify the behavior for
fmemopen(), and also to contact the glibc developers to get their
feedback.

+Bug 0000658: Undefined/unspecified behavior clauses in description of
open have race conditions OPEN
http://austingroupbugs.net/view.php?id=658
It was noted that there is some overlap with changes in TC1. Eric took an
action to update the proposal to resolve the overlaps appropriately.

+Bug 0000615: pthread_setcancelstate should be async-signal-safe OPEN
http://austingroupbugs.net/view.php?id=615
We now have reports on AIX and Apple. Jim to report back on whether
pthread_cancelstate() is async-signal-safe on Solaris. Andrew to ask
HP whether pthread_cancelstate() is async-signal-safe on HP-UX.


+Bug 0000672: Necessary step(s) to synchronize filename operations on disk
OPEN
http://austingroupbugs.net/view.php?id=672

Geoff has a new proposed resolution in note 1618. Decided to solicit input
from FS developers. Eric to go to Linux, David to AIX and Jim to Solaris.
Jim has completed his action (see bugnote 1691).
Andrew should chase HP and Apple for input.

+Bug 0000663: Specification of str[n]casecmp is ambiguous reopened
http://austingroupbugs.net/view.php?id=663

Action on David to follow up with the IBM developers about the EBCDIC
collation sequence.

Bug 696 either NAME_MAX shouldn't be optional, or readdir_r() needs clarification
http://www.austingroupbugs.net/view.php?id=696

Don has an action to propose a resolution.

Bug 0000721: Internal storage vs static storage OPEN
http://austingroupbugs.net/view.php?id=721

This item is still open.

Bug 0000375: Extend test/[...] conditionals: ==, <, >, -nt, -ot, -ef OPEN
http://austingroupbugs.net/view.php?id=375

This is still left open due to discussions pending on the reflector.

Bug 0000789: Add set -o pipefail OPEN
http://austingroupbugs.net/view.php?id=789


* Current Business


- Open Actions
Bug #851: pthread_atfork orphans handlers in unloaded shared libraries OPEN
http://www.austingroupbugs.net/view.php?id=851

Action item: Andrew should try and contact to Finnbarr Murphy.
(Status: Andrew has sent a query to Finnbarr via linked.in
and also to his direct email - no update this week)


Bug #854: requirement for additional built-in utilities to be searched for via $PATH was not and is not existing practice OPEN
http://austingroupbugs.net/view.php?id=854

Action: Andrew to ask David Korn to comment on this bug and the previous email discussion of the issue (seq 21270).

Action completed - awaiting response from David.

Bug #859: Add posix_random family of interfaces OPEN
http://austingroupbugs.net/view.php?id=859

Action on The Open Group Base WG to respond whether they will sponsor.



- Bug processing


Bug #857: Make rules which do not create the target file or do unexpected things with its timestamp Accepted as Marked
http://austingroupbugs.net/view.php?id=857

Richard has prepared a further response in bugnote 2393. This was reviewed
and reworked during the meeting.

On page 2937 lines 97106-97107 (make Extended Description), change from:

A target is considered out-of-date if it is older than any of its
prerequisites or if it does not exist.


to:

A target shall be considered up-to-date if it exists and is
newer than all of its dependencies, or if it has already been
made up-to-date by the current invocation of make (regardless
of the target's existence or age). A target may also be considered
up-to-date if it exists, is the same age as one or more of its
prerequisites, and is newer than the remaining prerequisites
(if any).


On page 2937 lines 97111-97113 (make Extended Description), change from:

After make has ensured that all of the prerequisites of a target
are up-to-date and if the target is out-of-date, the commands
associated with the target entry shall be executed. If there are
no commands listed for the target, the target shall be treated as
up-to-date.


to:

To ensure that a target is up-to-date, make shall ensure that all
of the prerequisites of a target are up-to-date, then check to
see if the target itself is up-to-date. If the target is not
up-to-date, the target shall be made up-to-date by executing the
rule's commands (if any). If the target does not exist after the
target has been successfully made up-to-date, the target shall
be treated as being newer than any target for which it is a
prerequisite.

If a target exists and there is neither a target rule nor an
inference rule for the target, the target shall be considered
up-to-date. It shall be an error if make attempts to ensure that
a target is up-to-date but the target does not exist and there
is neither a target rule nor an inference rule for the target.


After page 2948 line 97603 add a new paragraph to the APPLICATION USAGE:

Shell command sequences like "make; cp original copy; make" may
have problems on filesystems where the timestamp resolution is
the minimum (1 second) required by the standard and where make
considers identical timestamps to be up to date. Conversely, rules
like "copy: original; cp -p original copy" will result in redundant
work on make implementations that consider identical timestamps
to be out of date.


After page 2954 line 97847 add a new paragraph to the RATIONALE:

On most historic systems, the make utility considered a target
with a prerequisite that had an identical timestamp as up-to-date.
The HP-UX implementation of make treated it as out-of-date. The
standard now allows either behavior, but implementations are
encouraged to follow the example set by HP-UX. This is especially
important on filesystems where the timestamp resolution is the
minimum (1 second) required by the standard. All implementations
of make should make full use of the finest timestamp resolution
available on the filesystems holding targets and prerequisites
to ensure that targets are up-to-date even for prerequisite files
with timestamps that were updated within the same second. However,
if the timestamp resolutions of the filesystems containing a
target and a prerequisite are different, the timestamp with the
more precise resolution should be rounded down to the resolution
of the less precise timestamp for the comparison.


Bug #867 typographical issue in Shell Command Language 2.6.2 OPEN
http://austingroupbugs.net/view.php?id=867

We discussed this but did not have time to close it on the call.
Richard has proposed the resolution to be discussed next week (see bugnote 2397)

On page 2329 lines 73947-73947 delete:

(For example, ${foo-bar}xyz} would result in the expansion of foo followed by the string xyz} if foo is set, else the string <tt>"barxyz}"</tt>).


After page 2330 line 74013 add:

${parameter-word}

This example demonstrates the difference between unset and set to the empty string, as well as the rules for finding the delimiting close brace.

foo=asdf
echo ${foo-bar}xyz}
asdfxyz}
foo=
echo ${foo-bar}xyz}
xyz}
unset foo
echo ${foo-bar}xyz}
barxyz}

(see online for exact bolding of output http://austingroupbugs.net/view.php?id=867)


Next Steps
----------
The next call is on October 2, 2014 (a Thursday)
(Apologies from Andrew for next time)

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-aA9aGynHYqB/thfjNshNs9i2O/***@public.gmane.org:9001/p/201x-mm-dd
password=2115756#

--------
Andrew Josey The Open Group
Austin Group Chair Apex Plaza, Forbury Road
Email: a.josey-7882/***@public.gmane.org Reading,Berks.RG1 1AX,England
Tel:[phone] US fax: [phone]
Mobile:[phone] UK fax: [phone]