Understood, can we use any lessons learned there and apply them to what we have here?
On Thu, Jul 28, 2011 at 5:37 AM, George Niculae <[email protected]> wrote: > On Thu, Jul 28, 2011 at 12:30 PM, Michael Picher <[email protected]> > wrote: > > 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. > > > > Please mind that this is fixed in 4.6 so only a 4.4 issue > > George > _______________________________________________ > 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/
