Carolyn Beeton wrote: > > >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of >> Worley, Dale (BL60:9D30) >> Sent: Wednesday, October 15, 2008 3:01 PM >> To: sipX-dev >> Subject: [sipX-dev] ConfigurationTestFailed >> >> When sipXsupervisor discovers a configuration test failed, is >> that condition permanent, or if sipXconfig orders the >> component restarted, does sipXsupervisor re-run the config >> test to see if the configuration has been fixed? (I'm seeing >> symptoms that suggest that sipXsupervisor does not clear the >> error condition.) >> >> Dale >> > > Something will have to happen to kick supervisor to recheck. > Restart would do it, or if sipXconfig sets the version (which it isn't > doing at all yet - I think there is a patch pending for that) or > replicates a file.
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. 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
