Section 1.4 of the Commands and Utilities Volume of the standard (Utility
Description Defaults) already does this in the CONSEQUENCES OF ERRORS section
on P2303-2304, L74122-74151 in P1003.1-202x Draft 2 and on P2341-2342,
L74540-74569 in P1003.1-2017. Note especially:
The following shall apply to each utility, unless
otherwise stated:
... ... ...
• When an unrecoverable error condition is
encountered, the utility shall exit with a
non-zero exit status.
• A diagnostic message shall be written to
standard error whenever an error condition
occurs.
Cheers,
Don Cragun, IEEE PASC OR
> On Jun 24, 2021, at 12:18 PM, Vincent Lefevre via austin-group-l at The Open
> Group <[email protected]> wrote:
>
> Shouldn't POSIX require that when a utility cannot write its output
> (e.g. due to ENOSPC or EPIPE), it shall be regarded as an error, i.e.
> the exit status be non zero, with a diagnostic message if possible?
>
> --
> Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
>
