public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: BGINFO4X <bginfo4x@kztsoftware.com>
To: cygwin@cygwin.com
Subject: Re: interactive-services-detection not started on 32-bit cywin executables
Date: Fri, 17 Jan 2014 12:08:00 -0000	[thread overview]
Message-ID: <CAO2ddnZo51aGT-cjjxjTbvNmXtBkq4vRr4-E-6YXAVa_YcwYTw@mail.gmail.com> (raw)
In-Reply-To: <CAO2ddnY3TFjiaoYr6JtWECWprLBae==9isGX+CXOBhec3OWi-w@mail.gmail.com>

Hello,

I attach here my tests to clarify:

#Test1 - Only bash
C:\cywin\bin\bash.exe

Result: bash exits. Interactive window not opened.

#Test2 - Two programs
C:\cywin\bin\bash.exe
"%WD%..\BGBINARIES\Window\Window.exe"

Result: Interactive window opened: you can find only Window.exe opened.

#Test3 - Bash started via "start"
start "test" C:\cywin\bin\bash.exe
"%WD%..\BGBINARIES\Window\Window.exe"

Result: Interactive window opened: you can find both programs opened.

Conclusions:
1- What opens the interactive window is a program that doesn't exit.
2- bash.exe never opens the interactive window because it exits,or it
doesn't exit if it is launched with the start command(test3).
3- bash.exe launched with start command is started (test3), but the
interactive window is opened due to Window.exe (that doesn't exit).

Thanks a lot for your time.




2014/1/17 BGINFO4X <bginfo4x@kztsoftware.com>:
>> On 1/16/2014 12:10 PM, BGINFO4X wrote:
>>>
>>> Hello everybody,
>>>
>>> I have a "Windows service implementation of cygwin" via NSSM
>>> (http://nssm.cc/). I use cygwin 1.7.27 32 bits.
>>>
>>> If I configure the service as "allow service to interact with
>>> desktop", the UIODETEC.exe is not started, so I can't see the console.
>>>
>>> Do you know why uiodetect is not started with 32-bit cygwin
>>> executables? Any workaround? I tested it on W2008 R2 (64 bits) and W7
>>> 32 bits
>
> Sorry, I was half wrong: on windows 7 - 32 bits it works.
>
> The problem happens only on W2008R2 (64 bits) with cygwin 32 binaries.
>
> 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.
>
> Could you help me?
>
> Thanks a lot for your time.
>
>
>>
>> --
>> 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
>>

--
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

  reply	other threads:[~2014-01-17 12:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 11:53 Fwd: " BGINFO4X
2014-01-17 12:08 ` BGINFO4X [this message]
2014-01-19 22:49   ` Larry Hall (Cygwin)
     [not found]     ` <CAO2ddnZQ4otrozE-BqKzLn66wyL6oE8uVHLUA7zjF3T52kwg7g@mail.gmail.com>
2014-01-21 17:21       ` BGINFO4X
  -- strict thread matches above, loose matches on Subject: below --
2014-01-16 17:10 BGINFO4X
2014-01-16 18:56 ` Larry Hall (Cygwin)
2014-01-16 19:15 ` Larry Hall (Cygwin)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAO2ddnZo51aGT-cjjxjTbvNmXtBkq4vRr4-E-6YXAVa_YcwYTw@mail.gmail.com \
    --to=bginfo4x@kztsoftware.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).