Frédéric MOHIER

@ddurieux : this may explain some of the strange behaviors we noticed recently about *poudriere* or the very old launched checks ... I suppose so

Perharps only sending the new configuration to the modules would be enough. The parent daemon should not stop the module if it is still prenset in the new received configuration

@palvarezcordoba : this one us the correct branch that I will merge after some more testings ... sory for the mess 😉

Hello sorry but it is now more than 2 years that I maintained this project by myself. This year I decided to drop off and I did not renewed the...

The recommended configuration way: - do not update the default shipped files (*alignak.ini*, *alignak.d/daemons.ini*, *alignak.d/modules.ini*) - add some extra files in the *alignak.d* directory 1. Adding a daemon or module...

For the same reason, having a receiver in a realm when no passive checks are expected is also of no interest

Note that even the broker may not be mandatory if no modules are to be attached

All the information provided in the `update_program_status` brok by all the schedulers are the same, except for the *running* information: program start time, ... each scheduler has its own start...

+1

Some things changed with the last *fpm* version ... RPM installation runs the `post-install.sh` script and FreeBSD looks ok but to be tested!