[1003.1(2016/18)/Issue7+TC2 0001621]: Add "null terminator" definition, adjust getdelim(3) usage accordingly

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1621 == Reported By:steffen Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001621]: Add "null terminator" definition, adjust getdelim(3) usage accordingly

The following issue has been RESOLVED. == https://austingroupbugs.net/view.php?id=1621 == Reported By:steffen Assigned To:

[1003.1(2008)/Issue 7 0000243]: Add -print0 to "find"

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=243 == Reported By:dwheeler Assigned To:

[1003.1(2008)/Issue 7 0000561]: NUL-termination of sun_path in Unix sockets

The issue 0001593 has been set as DUPLICATE OF the following issue. == https://austingroupbugs.net/view.php?id=561 == Reported By:eblake

[Issue 8 drafts 0001593]: specify whether struct sockaddr_un.sun_path can be a flexible array member

The following issue has been set as DUPLICATE OF issue 561. == https://austingroupbugs.net/view.php?id=1593 == Reported By:jscott0

[Issue 8 drafts 0001593]: specify whether struct sockaddr_un.sun_path can be a flexible array member

The following issue has been CLOSED. == https://austingroupbugs.net/view.php?id=1593 == Reported By:jscott0 Assigned To:

[1003.1(2008)/Issue 7 0000245]: Add -0 option to shell's "read"

The following issue has been set as DUPLICATE OF issue 243. == https://austingroupbugs.net/view.php?id=245 == Reported By:dwheeler

[1003.1(2008)/Issue 7 0000245]: Add -0 option to shell's "read"

The following issue has been CLOSED. == https://austingroupbugs.net/view.php?id=245 == Reported By:dwheeler Assigned To:

[1003.1(2008)/Issue 7 0000243]: Add -print0 to "find"

The issue 245 has been set as DUPLICATE OF the following issue. == https://austingroupbugs.net/view.php?id=243 == Reported By:dwheeler

[1003.1(2008)/Issue 7 0000244]: Add -0 to xargs

The following issue has been CLOSED. == https://austingroupbugs.net/view.php?id=244 == Reported By:dwheeler Assigned To:

[1003.1(2008)/Issue 7 0000244]: Add -0 to xargs

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=244 == Reported By:dwheeler Assigned To:

[1003.1(2008)/Issue 7 0000244]: Add -0 to xargs

The following issue has been set as DUPLICATE OF issue 243. == https://austingroupbugs.net/view.php?id=244 == Reported By:dwheeler

[1003.1(2008)/Issue 7 0000243]: Add -print0 to "find"

The issue 244 has been set as DUPLICATE OF the following issue. == https://austingroupbugs.net/view.php?id=243 == Reported By:dwheeler

[1003.1(2008)/Issue 7 0000245]: Add -0 option to shell's "read"

A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=245 == Reported By:dwheeler Assigned To:

Re: [1003.1(2008)/Issue 7 0000243]: Add -print0 to "find"

2023-01-09 16:20:13 +, Austin Group Bug Tracker via austin-group-l at The Open Group: [...] > On page 3365 line 114593 section xargs (DESCRIPTION), [...] > If the -0 option is specified, the application shall ensure that > arguments in the standard input are separated by null bytes. [...]

Re: Shell vs. read(2) errors on the script

On 1/8/23 9:39 AM, Thorsten Glaser via austin-group-l at The Open Group wrote: There are two questions here: ① Should shell script read errors be treated as EOF, as is practice? ② If not, what should the shell do upon encountering one? It's pretty clear that a non-interactive shell can't