| delorie.com/archives/browse.cgi | search |
On Jul 3 10:18, Julio Costa wrote: > Let me rephrase that in three questions: > "What happens if we launch commands without a console created?" That's actually the same question as the next one, isn't it? > "What are the type of programs that really need that console?" Cygwin processes don't worry about the console. They use what they get as file descriptors and live with that. Native processes exist in two variations. Some of them just use the stdio handles like Cygwin processes. Some of them require to be run in a console becasue they use Console I/O functions directly. These applications will fail miserably in a Cygwin environment not attached to a console. Unfortunately there are quite a lot of them used for Windows system administration. At least that's as far as I rememeber this whole issue. I may have forgotten some aspect, but I'm fairly sure that we can drop the hidden console business as far as only Cygwin processes are affected. > "Is it possible to identify them prior to launch them?" Cygwin checks for a Cygwin application prior to execv it. Not a Cygwin application == may need a console. I have some testing code which only tries to create an invisible console if the application to execv is not a Cygwin application. It seems to work nicely. I'm just not sure if it's really *that* simple... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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 |