On Fri, Feb 13, 2015 at 05:10:42PM +, Pádraig Brady wrote:
> bash though seems to connect the stdout of the process substitution
> to the pipeline, which seems like a bug:
> $ : | tee >(md5sum) | sha1sum
> 253a7a49edee354f35b2e416554127cf29c85724 -
md5sum inherits the anonymous pipe to sha1su
I was expecting bash to handle SIGPIPE specially here,
as in this context it's informational rather than an indication of error.
I.E. if a command to the right actually does fail
the status is set to that fail and the resulting SIGPIPEs
to the left are inconsequential to the status.
If no command f
zsh behaves as I expected:
% : | tee >(md5sum) | sha1sum
da39a3ee5e6b4b0d3255bfef95601890afd80709 -
d41d8cd98f00b204e9800998ecf8427e -
bash though seems to connect the stdout of the process substitution
to the pipeline, which seems like a bug:
$ : | tee >(md5sum) | sha1sum
253a7a49edee354f35b2e4
On 2/12/15 9:06 AM, gregrwm wrote:
> i now suspect bash does not properly handle EINTR while handling history.
Maybe. There's not enough information here to say.
> this just happened:
> bash: history: write error: Interrupted system call
What command did you use? Writing the history to stdout
