Woof!
On Tue, 24 Mar 2009 14:51:20 -0400, Damian Krzeminski <[email protected]> wrote: > Previously every configuration file was replicated slightly differently and > sipXconfig could make case-by-case decision if replicating a file requires > restart. But now we use common replication infrastructure that assumes that > every configuration file replication needs to be followed by service restart. Hmm, not a good assumption. If it doesn't already have it, sipXsupervisor config files should have a flag that says if a restart is needed for a change of a given config file (as it knows what services use what files). Then it should simply be a matter of either asking sipXsupervisor for this, or just telling it to restart the effected services when the file is replicated if needed. --Woof! _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
