Minutes of the 15th April 2024 Teleconference    Austin-1399 Page 1 of 1
Submitted by Andrew Josey, The Open Group.         18th April 2024


Attendees:
    Don Cragun, IEEE SA OR
    Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
    Andrew Josey, The Open Group (partial)
    Eric Blake, Red Hat, The Open Group OR
    Geoff Clare, The Open Group
    Eric Ackermann, CISPA
   
Apologies
    Mark Ziegast, SHware Systems Dev

* General news

The IEEE approval meeting is due May 6.

The ISO ballot has opened and completes at the end of June.

* Current Business

1797: strftime "%s" should be able to examine tm_gmtoff OPEN
https://austingroupbugs.net/bug_view_page.php?bug_id=1797

We will continue this item next time that Paul is available (expected in April).



Bug 1810: fdopen() can only be used once per file descriptor Accepted as Marked
https://austingroupbugs.net/view.php?id=1810

This item is tagged for TC1-2024.

After page 899 line 30638, add to fclose() APPLICATION USAGE:

    If the file descriptor associated with the stream has already
    been closed, fclose() fails with an [EBADF] error (after it
    deallocates the stream). However, in the event that the same
    file descriptor number is allocated by some other operation
    (such as dup(), fopen(), open(), pipe(), socket(), and so forth),
    before fclose() is called, the fclose() call will close this
    newly allocated file descriptor instead. Therefore, applications
    which close the file descriptor before calling fclose() should
    ensure that they do not perform any file open operations in
    between closing the file descriptor and calling fclose(). This
    also applies in the event that two streams have the same
    associated file descriptor; calling fclose() on the first stream
    closes the file descriptor associated with both streams, and
    then calling fclose() on the second stream has the same risk
    described above. See also xref to P522, L18532 XSH 2.5.1
    Interaction of File Descriptors and Standard I/O Streams.


After page 918 line 31349, add to fdopen() APPLICATION USAGE:

    See also the APPLICATION USAGE for fclose().

Bug 1812: Support xargs -P 0 Accepted as Marked
https://austingroupbugs.net/view.php?id=1812

This item is tagged for Issue 9.

After making the page 3601 line 123232 change from bug 1801, change:
    If the value of maxprocs is non-positive, the behavior is unspecified.
to:
    If the value of maxprocs is zero, the system heuristically
    attempts to minimize total runtime by executing multiple
    invocations of utility without waiting for previous executions
    to complete (e.g., by choosing the number of such invocations
    based on the number of available processors).

    If the value of maxprocs is negative, the behavior is unspecified.

Bug 1813: generic xargs description cleanups OPEN
https://austingroupbugs.net/view.php?id=1813

We will continue on this item next time.

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

The next call is on:
  Thu 2024-04-18 (WEBEX meeting - general bugs) 
  Mon 2024-04-22 NO MEETING
  Thu 2024-04-25 (WEBEX meeting - general bugs) (note different webex)

Apologies in advance:
2024-04-25 Nick Stoughton

The calls are for 90 minutes

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

Please check the calendar invites for dial in details.

Bugs are at:
https://austingroupbugs.net

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

https://posix.rhansen.org/p/20xx-mm-dd

(For write access this uses The Open Group single sign on,
for those individuals with gitlab.opengroup.org accounts.
Please contact Andrew if you need to be setup)