Right. The issue will be how do the slaves pickup any configuration changes.
I see a couple possible options (through my rose colored non-developer glasses): An option to not restart slaves, or to schedule restarting the slaves individually at different times. Fix the services that are required on the slave (distributed) servers to be able to pickup configuration changes without restarting. On Wed, Jul 27, 2011 at 9:22 PM, Douglas Hubler <[email protected]> wrote: > in 4.4.0, i have a system w/5 locations > primary > slave01 > slave02 > slave03 > slave04 > > > If i send profiles to location slave04, then after it's done, then the > proxy/registrar and media relay on primary, slave01-slave03 are all > asked to restart. The is an issue because if I'm really having > trouble w/slave04, the last thing i want to do is reboot the other > locations that are presumably healthy. > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- Michael Picher eZuce Director of Technical Services O.978-296-1005 X2015 M.207-956-0262 @mpicher <http://twitter.com/mpicher> www.ezuce.com
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
