Hi Darren, you can easily setup a Windows service (or a *nix demon) for an individual JRUN instance and control it this way.
<http://www.bloginblack.de/archives/000295.cfm> (Actually that's a post from before I started to post in English :-) Roughly the core content: --- ... bin/jrunsvc -install jrun_server service-name service-display service- description parameters: jrun_server: instance name service-name: service name service-display: service display name service-description: service description ... --- Cheers, Kai ____________________________________________ Kai Koenig Director & Software Solutions Architect Ventego Creative Ltd 154 Parkvale Road, Karori Wellington, New Zealand Office: +64 4 476 6781 Mobile: +64 21 928 365 e-mail: [EMAIL PROTECTED] web: http://www.ventego-creative.co.nz blog: http://www.bloginblack.de >If you have a JRUN setup with multiple JRUN containers on the one JRUN >server, where is the setting that controls whether any individual >container is automatically started up when the JRUN service fires up >after a system reboot? >I've got a collection of containers on several jrun servers, and most >of the containers don't automatically start up after a system reboot, >and need to be manually started. After a restart, its always the same >containers that are running and the same containers that are stopped. >I think there's an XML setting for this, but trawling through all the >XML files manually has revealed nothing, and looking in the JRUN >documentation and Google searching has also revealed nothing. > >Anyone have any ideas about this? > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
