This is the mail archive of the cygwin 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] |
On 1/17/2014 7:08 AM, BGINFO4X wrote:
Hello, I attach here my tests to clarify: #Test1 - Only bash C:\cywin\bin\bash.exe Result: bash exits. Interactive window not opened.
<snip>
For example, when launching only bash.exe as a service, bash EXITS immediately. But, If I launch bash.exe and then another win32bit executable (ex: msys sh.exe), then OIUDetect is "captured" and bash.exe doesn't exit. So "it seems that 32 bits cygwin are not correctly managed on 64 bits systems"The only workaround I can think of is to start the uiodetect service.No, this is not the question: uiodetect is always started.
Yes, you know this now but this was the question you were asking in the last round. Fortunately, you do not need my answer now. :-)
Could you help me?
You're invoking bash non-interactively. Since you want an interactive shell, you should be using the '-i' flag. -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |