All
Enclosed are the minutes from the Thursday call this week
regards
Andrew
--------------
Minutes of the 9th February 2023 Teleconference Austin-1290 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 10th February 2023
Attendees:
Don Cragun, IEEE PASC OR
Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR
Andrew Josey, The Open Group
Eric Ackermann, HPI, University of Potsdam
Geoff Clare, The Open Group
Mark Ziegast, SHware Systems Dev.
Eric Blake, Red Hat, The Open Group OR (2nd hour only)
Tom Thompson, IEEE
* General news
A reminder that the closing date for sign for IEEE balloting is
18th February (note to all that this is not a requirement, but an
option and aimed at IEEE members).
It was also noted that the ISO CIB ballot closes on 10th February.
* Carried Forward
This section trimmed -- see Austin/1264
Bug 1406: clarification of SEEK_END when current pointer doesn't match buffer
size OPEN
https://austingroupbugs.net/view.php?id=1406
Actions carried forward:
ACTION: Andrew to contact Rich Felker (dalias) and Alan Coopersmith (Solaris)
for feedback.
Completed
ACTION: Eric B to contact glibc folks.
Bug 1616: Standardize mktemp utility OPEN
https://austingroupbugs.net/view.php?id=1616
We will need a sponsor; it is not suitable for inclusion in Issue 8.
ACTION: Eric to ask The Open Group to sponsor adding the mktemp utility
(for Issue 9).
Bug 1291: Add method to obtain pthread attributes OPEN
https://austingroupbugs.net/view.php?id=1291
Needs additional details and sponsor for Issue 9
Bug 0000251: Forbid newline, or even bytes 1 through 31 (inclusive), in
filenames OPEN
http://austingroupbugs.net/view.php?id=251
(brought forward)
Don has an action to produce a proposal.
Bug 1622: Standardize getpeereid function OPEN
https://austingroupbugs.net/view.php?id=1622
Action: Eric B to ask The Open Group if they are willing to sponsor this
function for Issue 9.
* Current Business
Bug 1629: Shell vs. read(2) errors on the script OPEN
https://austingroupbugs.net/view.php?id=1629
A proposed resolution has been added, it is being left open for
feedback until 2023-03-09.
See bugnote 0006145 (included here)
The following is a proposed resolution for this bug, but it is not
existing practice in almost all shells (they treat a read error
like end-of-file) and so we would like feedback from shell authors
to indicate whether they are willing to make changes to follow these
new requirements. The rationale for requesting this change in
behavior is that executing the partial line after getting a read
error is really not a good thing for any shell to do. Consider a
shell script that contains the command:
rm -f -- *.tmp
If the shell successfully reads "rm -f -- *" and then gets an error
when it tries to read ".tmp", it will execute "rm -f -- *", resulting
in data loss.
Please send feedback by March 9, 2023.
Add a row (D2.1 p2330) to the table in 2.8.1 Consequences of Shell
Errors:
Read error when reading commands | shall exit *4 | shall exit *4 | yes
and add a new note after the table:
4. If a partial command was read before the read error occurred,
that partial command shall not be executed.
Add to the exit status section of the sh utility on P3155 after L107008:
1-126
A read error was detected while reading commands.
Change P3155, L107009-107011 in the exit status section of the sh utility from:
1-125
A non-interactive shell detected an error other than
command_file not found or executable, including but not
limited to syntax, redirection, or variable assignment
errors.
to:
1-125
A non-interactive shell detected an error other than
command_file not found, command_file not executable, or a
read error while reading commands; including but not limited
to syntax, redirection, or variable assignment errors.
Bug 1630: Alias names
https://austingroupbugs.net/view.php?id=1630 OPEN
We started this item and we will continue with this item next time.
Next Steps
----------
The next calls are on:
Mon 2023-02-13 (general bugs)
Thu 2023-02-16 (general bugs)
Apologies in advance:
* Mark Ziegast, 2023-02-13
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: a.jo...@opengroup.org
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
