Minutes of the 17th September 2020 Teleconference Austin-1064 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 18th September 2020 Attendees: Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Joerg Schilling, FOKUS Fraunhofer Geoff Clare, The Open Group Eric Ackermann, HPI, University of Potsdam Eric Blake, Red Hat, The Open Group OR Richard Hansen Andrew Josey, The Open Group Tom Thompson, IEEE Apologies: None * General news This was the first meeting with new authentication in place. Writeable access to the etherpad now needs users to authenticate via gitlab.opengroup.org. Read access is now permitted without login. Please note that you need to have a working login for www.opengroup.org. If you are having issues please contact Andrew. * 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 https://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. * Current Business Bug 0000697: Adding of a getdirentries() function https://www.austingroupbugs.net/view.php?id=697 This has a separate etherpad page. https://posix.rhansen.org/p/bug697 We will continue after the Issue 8 draft 1 bug resolution Bug #1363: out of date wait() RATIONALE regarding core dump indication Accepted https://www.austingroupbugs.net/view.php?id=1363 Bug #1370: Where change history starts Accepted as Marked https://www.austingroupbugs.net/view.php?id=1370 On page 3433 line 117421 (XRAT B.1.1) change: The CHANGE HISTORY section for each entry details the technical changes that have been made to that entry from Issue 5. Changes between earlier versions of the base document and Issue 5 are not included. to: The CHANGE HISTORY section for each entry details the technical changes that have been made in Issue 5 and later. Changes made before Issue 5 are not included. On page 3555 line 122714 (XRAT C.1.1) change: The CHANGE HISTORY section for each utility describes technical changes made to that utility from Issue 5. Changes between earlier versions of the base document and Issue 5 are not included. to: The CHANGE HISTORY section for each utility describes technical changes made to that utility in Issue 5 and later. Changes made before Issue 5 are not included. Bug #1383: Make "Application Usage" less confusing. Accept as Marked https://www.austingroupbugs.net/view.php?id=1383 On page 878 line 29980 (fork() application usage), change: When a multi-threaded process calls fork(), although all memory that is addressable in the calling thread remains addressable in the child, there is no guarantee that the contents of thread-specific memory, such as stacks or thread-local storage, that was specific to other threads in the parent will still be the same in the child. This is because such memory could be treated as available in the child given that the threads it related to do not exist in the child, and consequently the processing performed in the child before fork() returns could make use of that memory. Therefore applications should avoid using in the child any pointers to thread-specific memory that were passed to the calling thread from other threads in the parent. to: When a multi-threaded process calls fork() or _Fork(), there is no guarantee that thread-specific memory (such as stacks or thread-local storage) associated with threads in the parent other than the calling thread will still be available in the child. This is because threads in the parent other than the calling thread do not exist in the child. Consequently, the implementation of fork() and _Fork() could remove that memory from the address space in the child, or reuse it for other purposes before returning or (in the case of fork()) calling any of the fork handlers registered by pthread_atfork(). Therefore, applications should avoid using any pointers to thread-specific memory in the child that were passed to the calling thread from other threads in the parent. Bug #1386: strftime RETURN VALUE and ERRORS problems OPEN https://www.austingroupbugs.net/view.php?id=1386 We did not complete discussion on this item and will continue next time. Gettext draft. We will return to this on a future call. The gettext draft in the etherpad is at https://posix.rhansen.org/p/gettext_draft https://posix.rhansen.org/p/gettext_split Next Steps ---------- The next calls are on: September 21st 2020 (Monday) This call will be for 60 minutes. September 24th 2020 (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. 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)