On 6/29/16 11:22 PM, Grisha Levit wrote:
> Thanks, the -n option does work around this.
> I was very surprised to see input going to a backgrounded process
You shouldn't be. When job control is active, bash doesn't modify the
standard input of any background process it starts, in case the job ge
Thanks, the -n option does work around this.
I was very surprised to see input going to a backgrounded process but it
seems that it is actually being stolen by the ssh control master process,
which is not under bash's control.
On 6/29/16 1:39 PM, Grisha Levit wrote:
> The observed condition is input getting split between the shell and the
> background process. I couldn’t figure out what the general case is to
> trigger this, but I can observe it when an ssh process with an open unix
> socket is placed in the background.
The observed condition is input getting split between the shell and the
background process. I couldn’t figure out what the general case is to
trigger this, but I can observe it when an ssh process with an open unix
socket is placed in the background.
Below is my recipe to reproduce. First step is
