subshell redirections which read stdin become unstoppable, interrupts hit the wrong process
sellout:~> ssh -t metropolis bash metropolis:~$ cat <(cat /dev/stdin) | cat ^CConnection to metropolis closed. zsh: exit 255 ssh -t metropolis bash sellout:~>
A ^D to attempt to get an EOF to the inner-most cat fails too, and I suspect it shouldn't.
The actual command I used was
metropolis:~$ comm -13 <(sed -e 's,root_i386/,,') wsdiff.log | wc -l
With which I now find that, without a wsdiff.log, may or may not screw up further input to a shell which may or may not be at the top level (I ended up with the shell only echoing every other character typed, but I'm not sure how/why).
Updated by Chris Jordan over 11 years ago
- Assignee set to OI SFW
- Difficulty set to Medium
- Tags set to bash
Julian and I both see this happen with bash, but not with ksh, even if /usr/bin/cat is used instead of the shell builtin like so:
/usr/bin/cat <(/usr/bin/cat -) | /usr/bin/cat
(ctrl-d or ctrl-c exits correctly on ksh, but kills the parent shell on bash)