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]
Other format: [Raw text]

Re: subprocess i/o interaction with shell (bash&cmd): shells compete for input with user program!


On Tue, Jul 22, 2003 at 04:41:18PM -0400, Sam Steingold wrote:
>> * In message <20030722172316.GC17916@redhat.com>
>> * On the subject of "Re: subprocess i/o interaction with shell (bash&cmd): shells compete for input with user program!"
>> * Sent on Tue, 22 Jul 2003 13:23:16 -0400
>> * Honorable Christopher Faylor <cgf-idd@cygwin.com> writes:
>>
>> On Tue, Jul 22, 2003 at 12:23:18PM -0400, Sam Steingold wrote:
>> >> Under cygwin you'd accomplish this by having the parent process use
>> >> one of the "exec" calls.
>> >
>> >nope.  doesn't work either.
>> >I get the same "input competition" when I use exec().
>> 
>> If you are using fork/exec, then sure, you'll get that.
>
>I am not using fork().  just plain exec().

Ok.  Then you're not building cygwin applications apparently.   Next
assumption is that you're using the -mno-cygwin option.

If the exec paradigm in cygwin was really broken, the mailing list would
be filled with people complaining about that fact.

cgf
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam@sourceware.org
and be permanently blocked from mailing lists at sources.redhat.com

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


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