Hi Lionel, I think it's good idea. I think that the 'apollo create' command should generate a bin/apollo-service script that does what your suggesting. Also I think we should not force folks to use the java service wrapper, while it's handy, there are several other watchdog processes available (like monit, and launchd) which could take care of restarting ActiveMQ on failure so, if anything perhaps we should optionally generate a second service script that uses the jsw.
Regards, Hiram FuseSource Web: http://fusesource.com/ Connect at CamelOne May 24-26 The Open Source Integration Conference On Thu, Apr 21, 2011 at 1:42 AM, Lionel Cons <[email protected]> wrote: > Hiram, > > Now that Apollo is getting more mature (beta), it's probably the right > time to improve its integration with the operating system. > > It would be good to have a solid init script to be put in /etc/init.d. > Here are the features that we would like to see: > - use a pid file > - handle the change of user (since the init script will run as root) > - handle status and stop even if the console (REST interface) is disabled > > Also, we currently use the Java wrapper with ActiveMQ 5.x. Is this > something you would recommend for Apollo? If yes, it should be > integrated with the init script... > > Cheers, > > Lionel >
