This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: O_NOCTTY flag sticky under Cygwin


On Tue, May 08, 2001 at 05:40:54PM +0400, Andrej Borsenkow wrote:
>It appears, that O_NOCTTY is sticky. I.e. if a tty was opened with this flag,
>it will never become a controlling tty. The following pseudo code:
>
>fd = open("/dev/pts/1", O_RDWR|O_NOCTTY);
>close(0);
>close(1);
>close(2);
>dup2(fd,0);
>
>does not make /dev/pts/1 controlling tty under Cygwin. It does it on most
>major Unix flavours (Solaris, Linux, BSD, AIX, HP-UX).
>
>If I understand SUS V2 correctly, this flag applies only to open() call
>itself:
>
>O_NOCTTY
>If set and path identifies a terminal device, open() will not cause the
>terminal device to become the controlling terminal for the process.

Hmm.  I made an obvious fix for this to Cygwin and Corinna reported that
this broke ssh.  Apparently something in ssh is relying on this
functionality.

I'll have to investigate more under linux.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]