Dale Worley wrote: > On Wed, 2008-10-15 at 15:53 -0400, Damian Krzeminski wrote: >> I am not sure if this is a proper strategy. If the configuration file is >> changed the service that depends on this configuration file should be >> notified and either restart itself or read the file if it can. >> >> If sipXconfig is responsible for restarting the services for which >> configuration files are generated than we keep dependency information in 2 >> places - sipXsupervisor and sipXconfig. That's going to be a source of >> problems. > > The case I'm worried about is when the system is started, a particular > service many not be able to run, either due to an absent config file or > failing its configtest. Once sipXconfig fixes the config problem and > (directly or indirectly) orders the service to be restarted, we need to > have the service started. Of necessity, we can't depend on the service > to be running, waiting for the config problem to be fixed. >
Good point. So sipXsupervisor (which knows exactly which files and when are pushed since it implements XML/RPC AP) should check if affected service is running and start it if it's not. If the service is running it should notify it about configuration change (or restart it if the service cannot dynamically update configuration). D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
