[Shinken-devel] One init.d script, multiple default/shinken files
Status: Beta
Brought to you by:
naparuba
From: nap <nap...@gm...> - 2011-04-18 13:40:15
|
Hi, We are looking with David about package creation. One think that look to be a problem is the "more than one init.d script". In fact, there is two ways for start daemons, the direct /etc/init.d/shinken-poller or with /etc/init.d/shinken way. But it's a huge problem for packagers, and quality checks just don't pass with it. So we are thinking about another way, more simple and efficient (we hope) : * only one init.d script for all daemons, the /etc/init.d/shinken one. * a common /etc/defaults/shinken file taht give all global parameters like path. * a /etc/defaults file for each daemons. with specific parameters, and a "enable-poller=1" parameter too With this, it will still be easy to : * setup a simple shinken for a beginer (one init.d script is enougth :) ) * setup distributed daemon. Just install the package you want, and if you install too much, disable what you do not want. It just need a cutting pass for the defaults/shinken file (keep global parameters, and put all other parameter in daemon specific files) and add a "look at what is enabled in the defaults files" pass in the init.d script. Then we will be good for deleting old init.d/shinken-* scripts :) So, good idea or not? Jean |