Hi, there's a difference between Unix and Windows here.
start/start.bat actually does bin/karaf server. On Unix, it does this in background (aka karaf server &) as Unix can "maintain" a process running in background. Unfortunately, on Windows, it's executed on DOS command terminal to keep the process running (if you close the DOS command, Karaf stops). Karaf Wrapper uses a "native" piece of code for Windows, to be integrated in Windows services. So, it's up to you to close the DOS command created. Regards JB On 15/05/2019 13:03, Paul Fraser wrote: > Hi, > > Using Installbuilder to create installers for Linux 64 and Win 64, to > run Karaf 4.2.5 in the background. > > The linux version (developed on a linux 64 machine) works well by using > '&' as argument to start script . The installer closes and no console > remains. > > The windows version installer (developed on win 10 machine) closes if an > '&' is used same as the linux version but a console remains containing > message > > "karaf.bat: Ignoring predefined value for KARAF_HOME" > > With no argument to start.bat in windows the installer does not close. > > Any suggestions as to how to handle the start script in windows? > > Paul Fraser > > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
