On Thu, 2008-10-30 at 11:00 -0400, Kevin Thorley wrote: > You're right, the domain-config that has been replicated will not match > the version that the running processes are using. However, I don't see > how this can be avoided (unless we replicate at the scheduled restart > time), and I don't think its a problem unless some services restart and > load the new one before the global restart is invoked. Regardless, we > can not force an admin to restart their whole system when they hit "Ok" > to add a new location
Restarting anything should always be an admin-initiated action with careful warnings. Adding an alias to some systems and not others isn't likely to cause failures, and if it does it's the sort of thing that people will recognize quickly, I think. Is there some indication we can put in the warning line "Some configuration will not be updated until you restart" ? _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
