daemons other than arbiter try to start even without a config file provided about alignak HOT 3 CLOSED

what I mean in the first time is : it's not a problem, imo, that the daemons others than arbiter try to start while no config file given to them.. they'll use all / any default values that they need and that is "hard-coded" somewhere in the code..

what I mean is that :

if we would had that (the "default" coded values) somewhere well defined (still say alignak.defaults), and independant from any other thing, then it's rather straightforward to be able to overhidde them with others values for when installed under a virtualenv, for instance.

from alignak.

it's not a problem, imo, that the daemons others than arbiter

even the arbiter could run without a config file.. but it's something else given it's a special daemon versus the others daemons.

from alignak.

Currently, thanks to #427, all the daemons (even arbiter) can start without a configuration file with default values. Their working dir is the current working directory ...

from alignak.