Problem redirecting stderr to pipe in subprocess

Christopher Faylor cgf-use-the-mailinglist-please@cygwin.com
Tue Oct 11 17:08:00 GMT 2011


On Tue, Oct 11, 2011 at 02:17:42PM +0200, Corinna Vinschen wrote:
>On Oct 10 18:06, Christopher Faylor wrote:
>> When the tty layer in Cygwin was first developed, the model (either in
>> my head or in reality) was "If you don't have a tty and open a tty, that
>> becomes your controlling tty".  But, apparently that model changed over
>> time to something more sensical where you have to explicitly use
>> ioctl(TIOCSCTTY) to set up a controlling terminal.
>
>I don't quite understand this.  The "If you don't have a tty and open a tty,
>that becomes your controlling tty" is standard POSIX behaviour, isn't it?
>SUSv4 open writes:
>
>  O_NOCTTY
>
>    If set and path identifies a terminal device, open() shall not
>    cause the terminal device to become the controlling terminal for
>    the process. If path does not identify a terminal device,
>    O_NOCTTY shall be ignored.
>
>The Linux man page contains basically the same.

Check out the linux info page.  It's more talkative.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple



More information about the Cygwin mailing list