nap a écrit : > For the global launch I don't know. It's easier to wrote the script, > but is is easier for the user? It's true he just need to launch one > init.d script to launch all, but at the begining it can be hard to > know that one daemon is not starting just because he missed to add the > good ini file.
The launcher try to lauch them all. If there is no configuration file (not the default case), the laucher script state : Launching xxxx skipped (no configuration) > But it's also true that with the package, the ini files will already > be installed, so no problem for them after all (the only one are > people who want to install it at the hand). So it sounds like a good > idea for the majority of users. > > Now how to find which damon to launch. By the ini files name? (broker > in it -> broker daemon). It's also an option : add a parameter: [daemon] # Should we start this module automatically when starting Shinken ? autostart=true/yes/1 -- Stéphane Urbanovski ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Shinken-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shinken-devel
