delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_NONE,UNPARSEABLE_RELAY |
X-Spam-Check-By: | sourceware.org |
X-Yahoo-SMTP: | jenXL62swBAWhMTL3wnej93oaS0ClBQOAKs8jbEbx_o- |
Date: | Tue, 11 Oct 2011 13:08:34 -0400 |
From: | Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: Problem redirecting stderr to pipe in subprocess |
Message-ID: | <20111011170834.GA4522@ednor.casa.cgf.cx> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <4E906DD1 DOT 50107 AT cornell DOT edu> <4E90C308 DOT 9090508 AT cornell DOT edu> <20111009235815 DOT GA18203 AT ednor DOT casa DOT cgf DOT cx> <20111010220608 DOT GA1568 AT ednor DOT casa DOT cgf DOT cx> <20111011121742 DOT GC21554 AT calimero DOT vinschen DOT de> |
MIME-Version: | 1.0 |
In-Reply-To: | <20111011121742.GC21554@calimero.vinschen.de> |
User-Agent: | Mutt/1.5.20 (2009-06-14) |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |