All
Enclosed are the minutes from this weeks meeting.

We now have a break until August 14th
regards
Andrew
-------------------

Minutes of the 24th July 2025 Teleconference    Austin-1465 Page 1 of 1
Submitted by Andrew Josey, The Open Group.        26th July 2025

Attendees:
    Andrew Josey, The Open Group 
    Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
    Geoff Clare, The Open Group
    Eric Ackermann, CISPA
    Haelwenn Monnier, The Open Group
    Eric Blake, Red Hat, The Open Group OR

Apologies
    Malia Zaman, IEEE-SA
    Mark Brown

* General business

We confirmed the calendar for upcoming meetings, the next meeting
is  August 14th.

Andrew reminded attendees of the links to the procedures of the Austin Group,
and the three bodies now present in the etherpad.


* Carried Forward

Bug 1927: Add sponge utility  
https://www.austingroupbugs.net/view.php?id=1927

[Action to Eric B] Start a 30-day request for comments on whether The Open 
Group should sponsor the addition of this interface.

glibc realloc() behavior

[Action to Eric B] - respond to the thread and invite Alejandro to
open a bug against POSIX if we still need to address wording issues

Update 2025-06-26: discussion on mailing lists is still ongoing;
EricB or Alejandro will open a bug soon

* New Business


Bug 1933: make: example 7 contains text for two separate topics
https://www.austingroupbugs.net/view.php?id=1933
Accepted, resolved, tc1-2024 tag

Bug 1934: ex's suspend command and job control
https://www.austingroupbugs.net/view.php?id=1934
Accepted as marked, resolved, tc1-2024 tag

On page 2841 line 94334 section ex (ASYNCHRONOUS EVENTS), change:
    <blockquote>The action taken for all other signals is
    unspecified.</blockquote>
to:
    <blockquote>The action taken for signals that stop the process
    (see [xref to <signal.h>]) shall be the default action. The
    action taken for all signals other than those that stop the
    process and those listed above is unspecified.</blockquote>

On page 2868 line 95402 section ex (suspend), change:
    <blockquote>Allow control to return to the invoking process;
    <i>ex</i> shall suspend itself as if it had received the SIGTSTP
    signal. The suspension shall occur only if job control is enabled
    in the invoking shell (see the description of <i>set</i>
    <b>-m</b>).</blockquote>
to:
    <blockquote>Suspend the process group to which <i>ex</i> belongs;
    <i>ex</i> shall send a SIGTSTP signal as if by a call to
    <tt>kill(0, SIGTSTP)</tt>, except that if the session ID of the
    session to which <i>ex</i> belongs is the same as its process
    group ID, no signal shall be sent.</blockquote>


After page 2902 line 96771 section ex (RATIONALE), add:
    <blockquote><b>Suspend</b>


    The <b>suspend</b> command is intended to mimic the action of
    the General Terminal Interface (see [xref to XBD 11.1.9 Special
    Characters]) for the SUSP character, by sending a SIGTSTP signal
    to the process group. The condition on the session ID being
    different is in order not to suspend the session leader, which
    would likely lead to a situation that the user may have difficulty
    recovering from.</blockquote>


and move lines 96772-96774 (Set) to before line 96746 (Substitute).


Bug 1935: posix_spawn file actions: in the context of the child or "as if" in 
the context of the child?
https://www.austingroupbugs.net/view.php?id=1935
Accepted as marked, resolved, tc1-2024 tag

On page 1590 line 53471 section posix_spawn_file_actions_addchdir(), change:
    <blockquote>[...] all file actions are processed in sequence
    in the context of the child at a point where the child process
    is still single-threaded.  [...]</blockquote>
to:
    <blockquote>[...] all file actions are processed in sequence
    as if in the context of the child at a point where the child
    process is still single-threaded.  [...]</blockquote>


On page 1591 line 53480 section posix_spawn_file_actions_addchdir(), change:
    <blockquote>File actions are performed in a new process created
    by <i>posix_spawn</i>() or <i>posix_spawnp</i>() in the same
    order that they were added to the file actions object.</blockquote>
to:
    <blockquote>File actions are performed as if in a new process
    created by <i>posix_spawn</i>() or <i>posix_spawnp</i>() in the
    same order that they were added to the file actions
    object.</blockquote>


On page 1592 line 53516 section posix_spawn_file_actions_addclose(), change:
    <blockquote>This transformation shall be as if the specified
    sequence of actions was performed exactly once, in the context
    of the spawned process (prior to execution of the new process
    image), in the order in which the actions were added to the
    object; additionally, when the new process image is executed,
    any file descriptor (from this new set) which has its FD_CLOEXEC
    flag set shall be closed (see [xref to posix_spawn( )]).</blockquote>
to:
    <blockquote>This transformation shall be as if the specified
    sequence of actions was:

    <ul>
    <li>performed exactly once</li>
    <li>performed in the context of the spawned process (prior to execution of 
the new process image)</li>
    <li>performed in the order in which the actions were added to the 
object</li>
    </ul>

    Additionally, when the new process image is executed, any file
    descriptor (from this new set) which has its FD_CLOEXEC flag
    set shall be closed (see [xref to posix_spawn( )]).</blockquote>


Bug 1936: timer_create synopsis uses clockid while rest of it's specification 
uses clock_id
https://www.austingroupbugs.net/view.php?id=1936
Accepted as marked, resolved, tc1-2024 tag

Replace clockid in synopsis with clock_id.

Bug 1937: Undefined behavior in tsearch EXAMPLES text
https://www.austingroupbugs.net/view.php?id=1937


We will start on this item next time.

* Next Steps

We will start on the bug 1937.

The next calls are on
    Thu 2025-08-14 (WEBEX meeting - general bugs)

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)

--------
Andrew Josey                    The Open Group
Austin Group Chair          
Email: [email protected] 
Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England

To learn how we maintain your privacy, please review The Open Group Privacy 
Statement at http://www.opengroup.org/privacy.
To unsubscribe/opt-out from this mailing list login to The Open Group 
collaboration portal at
https://collaboration.opengroup.org/operational/portal.php?action=unsub&listid=2481





Reply via email to