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
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
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
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
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
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.
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.
7 matches
Mail list logo