Job control in forced interactive mode upset if stderr is not the controlling tty

I have been playing with a terminal application which runs shells plumbed as below: fdwhat 0 pty slave 1 pty slave 2 some pipe To get the various shells being used to work, some of them require that '-i' be given for force interactive mode, fair enough. One problem

Job control in forced interactive mode upset if stderr is not the controlling tty

I have been playing with a terminal application which runs shells plumbed as below: fdwhat 0 pty slave 1 pty slave 2 some pipe To get the various shells being used to work, some of them require that '-i' be given for force interactive mode, fair enough. One problem